Digital Property Authentication and Management System

ABSTRACT

Systems and methods for digital property authentication and management are disclosed. A document representing a trade secret may be requested to be registered with a trade secret registry. A document obfuscation value corresponding to the document may be generated and may be registered with a blockchain. A record of the registration may be generated for the trade secret registry. The registry may be searchable and/or offer functionality such as valuation, insurance provision, and/or verification, among other benefits and functionalities.

RELATED APPLICATIONS

This application claims priority to and is a continuation of U.S. patentapplication Ser. No. 16/280,766, filed on Feb. 20, 2019, which willissue as U.S. Pat. No. 11,182,866 on Nov. 23, 2021, the entire contentsof which are incorporated herein by reference.

BACKGROUND

Trade secrets are can be valuable assets to companies and individuals.However, unlike other forms of intellectual property, governmentalregistration and/or grant of trade secret rights is not offered.Described herein are improvements in technology and solutions totechnical problems that can be used to, among other things, assist inthe protection of trade secrets.

BRIEF DESCRIPTION OF THE DRAWINGS

The detailed description is set forth below with reference to theaccompanying figures. In the figures, the left-most digit(s) of areference number identifies the figure in which the reference numberfirst appears. The use of the same reference numbers in differentfigures indicates similar or identical items. The systems depicted inthe accompanying figures are not to scale and components within thefigures may be depicted not to scale with each other.

FIG. 1 illustrates a schematic diagram of an example environment for adigital property authentication and management system.

FIG. 2 illustrates an example user interface displaying trade secretregistration functionality in accordance with a digital propertyauthentication and management system.

FIG. 3 illustrates an example user interface displaying trade secretmaintenance functionality in accordance with a digital propertyauthentication and management system.

FIG. 4 illustrates an example user interface displaying trade secretverification functionality in accordance with a digital propertyauthentication and management system.

FIG. 5 illustrates an example user interface displaying insurance-policyfunctionality in accordance with a digital property authentication andmanagement system.

FIG. 6 illustrates an example user interface displaying valuationfunctionality in accordance with a digital property authentication andmanagement system.

FIG. 7 illustrates an example user interface displaying access-controlfunctionality in accordance with a digital property authentication andmanagement system.

FIG. 8 illustrates a flow diagram of an example process for trade secretregistration in accordance with a digital property authentication andmanagement system.

FIG. 9 illustrates a flow diagram of an example process for trade secretverification in accordance with a digital property authentication andmanagement system.

FIG. 10 illustrates a flow diagram of an example process for digitalproperty authentication.

FIG. 11 illustrates a flow diagram of another example process fordigital property authentication.

FIG. 12 illustrates a flow diagram of another example process fordigital property authentication.

FIG. 13 illustrates a flow diagram of another example process fordigital property authentication.

FIG. 14 illustrates a flow diagram of an example process for identifyingdistinctions between documents associated with a digital propertyauthentication and management system.

FIG. 15 illustrates a flow diagram of an example process associated witha user interface in accordance with a digital property authenticationand management system.

FIG. 16 illustrates a flow diagram of another example process associatedwith a user interface in accordance with a digital propertyauthentication and management system.

FIG. 17 illustrates a flow diagram of an example process for digitalproperty management including document versioning.

FIG. 18 illustrates a flow diagram of an example process for digitalproperty management including trade-secret valuation.

FIG. 19 illustrates a flow diagram of an example process for digitalproperty management including access controls.

FIG. 20 illustrates a flow diagram of an example process for valuingproperty in accordance with a digital property authentication andmanagement system.

FIG. 21 illustrates a flow diagram of an example process for provisionof insurance policies in accordance with a digital propertyauthentication and management system.

FIG. 22 illustrates a flow diagram of an example process forregistration verification in accordance with a digital propertyauthentication and management system.

FIG. 23 illustrates a flow diagram of another example process forregistration verification in accordance with a digital propertyauthentication and management system.

DETAILED DESCRIPTION

Systems and methods for digital property authentication and managementare disclosed. Take, for example, a company or individual, describedherein as an entity, that owns one or more intellectual property assets.While some of those intellectual property assets may be registerable bya governmental entity, such as patents and trademarks being applied forand issued by the United State Patent and Trademark Office or copyrightsbeing registered by the United States Copyright Office, other types ofintellectual property, such as trade secrets, may not be registerable bya governmental entity. Additionally, information that may not meet aparticular (e.g., legal) definition of a trade secret, and/or may notmeet multiple, disparate definitions of a trade secret, sometimesreferred to as confidential information or know-how, may still bevaluable to the entity. In these and other examples, a system thatallows for the registration of such property (collectively referred toherein as “trade secret”) in a way that establishes indicia ofownership, credibility of possession, or other information useful inassessing protecting, insuring, or enforcing such property would bebeneficial to such entities.

The innovations described herein provide a digital propertyauthentication and management system that, among other things, enablesthe registration of information, documents and/or other property,provides user interfaces for registration and management of suchproperty, enables verification of registration and/or analysis ofpotentially misappropriated property, assists in asset valuation,assists in insurance provision, and utilizes data generated by and/oravailable to the system to increase functionality associated with theregistered property.

For example, a client-side device and/or system, herein described as anelectronic device, may include an application that enables a user of thedevice and/or system to provide input to the device. The input mayindicate a document, for example, that represents or is used to describea trade secret, and/or has been designated as a trade secret, and/or hasbeen designated as a document of importance to the entity. Theclient-side device and/or system may include a obfuscation componentthat may receive data representing the document and may generate adocument obfuscation value corresponding to the document. The documentobfuscation value may include, for example, a string of numbers and/orletters and may be based at least in part on the content of the documentand/or one or more information fields associated with the document. Itshould be noted that while document obfuscation value generation and useis described by way of example in this disclosure, one or more otherforms of digital obfuscation may be utilized in addition to, or insteadof, document obfuscation value generation. The digital obfuscationtechniques may allow for repeatable production of output data given thesame input data, such as the same document.

The client-side device and/or system may send, to a registry system, thedocument obfuscation value and, in examples, request data indicating arequest to register, in association with the trade secret registry, thedocument obfuscation value. The registry system may receive the documentobfuscation value and/or the request data and may initiate a process ofregistering the document obfuscation value in association with the tradesecret registry. For example, the registry system may send the documentobfuscation value and/or request data to a blockchain system managingone or more blockchains. In other examples, the client-side device maysend the document obfuscation value and/or request data to theblockchain system, as described more fully elsewhere herein. In stillother examples, the registry system and the client-side device may sendinstances of the document obfuscation value and/or the request data inparallel or near-parallel to the blockchain system. The request data mayindicate a request to register the document obfuscation value and/oridentifying information associated with the document obfuscation valueand/or the document with the blockchain. The blockchain system mayregister the document obfuscation value and/or the other informationdescribed herein in association with a block of the blockchain. Acryptographic document obfuscation value may be generated by theregistry system that may represent the block in the blockchain.Additionally, or alternatively, a time value may be determined thatindicates a time and/or day at which the document obfuscation valueand/or the other information described herein was registered with theblockchain. The blockchain system may then send the cryptographicdocument obfuscation value to the registry system associated with thetrade secret registry. The blockchain system may additionally, oralternatively, send the cryptographic document obfuscation value to theclient-side device, particularly in instances where the request data toregister the document obfuscation value was received from theclient-side device.

The registry system may generate a record in the trade secret registry.The record may include information associated with the trade secret. Forexample, the record may include data indicating an identifier of therecord, a naming indicator associated with the trade secret, adescription of the trade secret, a naming indicator associated with thedocument, one or more tags associated with the trade secret, a statusindicator for the trade secret, the document obfuscation value, a blocknumber associated with the block of the blockchain that the documentobfuscation value is registered with, the cryptographic documentobfuscation value, the time value, and/or one or more other types ofdata associated with the trade secret and/or registration of the tradesecret, such as valuation, insurance policy information, versioninginformation, etc. The registry system, in examples, may generateconfirmation data indicating that the record has been generated, and theconfirmation data may be sent to the client-side device and/or systemfor display via a user interface.

Additionally, or alternatively, the registry system may be configured toidentify, determine, and/or generate one or more indicia ofnonpublication of a trade secret. For example, a user of the registrysystem may provide information and/or documentation indicating that thetrade secret has not been published. In examples, the client-side devicemay be configured to analyze the document and/or informationcorresponding to the trade secret and may be configured to perform asearch of publicly-available databases and/or resources, such asInternet browsing and/or searching resources to determine whether theinformation and/or document corresponding to the trade secret has beenpublished. If the client-side device and/or the registry systemdetermines that the trade secret has not been published, the registrysystem may record indicia of such nonpublication. These indicia may beutilized, in examples, for insurance application and/or provision and/orfor legal means.

Additionally, or alternatively, the registry system may be configured todetermine whether the document to be registered with the trade secretregistry is unique with respect to other documents registered with thetrade secret registry. For example, the registry system may compare thedocument obfuscation value to one or more other document obfuscationvalues representing other documents registered with the trade secretregistry. If the document obfuscation value is the same as at least oneother registered document obfuscation value, then the registry systemmay determine that the document is not unique. In other examples, adegree of similarity may be determined between the document obfuscationvalue and the registered document obfuscation values, and if the degreeof similarity is greater than a threshold degree of similarity, thedocument may be determined to be not unique.

Additionally, or alternatively, the comparison of a to-be-registereddocument obfuscation value and registered document obfuscation valuesmay be utilized to determine if documents associated with the tradesecret registry are different versions of the same document, such as,for example, different versions of source code. For example, theregistry system may determine that a degree of similarity between twodocument obfuscation values is greater than a threshold degree ofsimilarity. Additionally, in examples, the registry system may determinethat an entity identifier indicating the entity associated with thedocuments is the same. In these and other examples, the registry systemmay determine that the two documents are different versions of the samedocument. The registry system may provide an indication of thisdetermination to the client-side device and/or system. Additionally, oralternatively, the registry system may generate a record for theto-be-registered document and may associate that record with the recordfor the registered document. A selectable link may be associated withthe records such that, upon selection of the link via a user interface,the associated record may be displayed.

In examples, the functionality described herein may be provided, atleast in part, via a user interface. The user interface may include oneor more selectable portions that, when selected, may cause one or moreprocessors to perform the operations described herein. For example, theuser interface may include selectable portions indicating an option toregister the trade secret in association with the trade secret registry,enabling a user to select and/or identify a document corresponding tothe trade secret, enabling a user to view a record of the trade secretregistry, enabling a user to acquire and/or view information associatedwith an insurance policy on the trade secret, enabling valuation of thetrade secret, enabling input of text for tag data generation, enablingsearching capabilities of records associated with the trade secretregistry and/or records associated with the entity, enablingverification that a document is registered with respect to the tradesecret registry, and/or displaying links and/or associations betweenrecords.

Additionally, or alternatively, the registry system may be configured todetermine a value for a trade secret and/or record information relevantto such a valuation. For example, during and/or after registration of atrade secret with the trade secret registry, an option to determine avalue for the trade secret and/or record information relevant to such avaluation may be displayed, such as via a user interface of theclient-side device and/or system. One or more dialog boxes and/or inputfields may be caused to be displayed, and the dialog boxes may requestinformation associated with the trade secret to aid in valuation of thetrade secret. Such information may include, for example, the type oftrade secret, an importance of the trade secret to the entity, entityrevenue and profit including particularly revenues and profitsattributable to the entity's use of the trade secret, the developmentcosts of the trade secret, entity value, date of trade secret creation,expected life of the trade secret, etc. Additionally, in examples, theinput fields may include a request for supporting documents that includeinformation that may be relevant to valuation of the trade secret. Inthese examples, the user may identify the supporting documents. Adocument obfuscation value may be generated for a given supportingdocument and/or the supporting document and/or the document obfuscationvalue may be registered in association with the blockchain. The recordfor the trade secret may include information associated with thesupporting document, such as the corresponding document obfuscationvalue and/or the cryptographic document obfuscation value correspondingto the block in the blockchain where the supporting document isregistered. The registry system may utilize some or all of thisinformation to generate a value associated with the trade secret.

Additionally, or alternatively, the registry system may be configured toutilize access controls to restrict access to certain records and/orportions of records. For example, access-control data may be stored inassociation with the registry system. The access-control data mayindicate who is authorized to view a given record and/or giveninformation associated with a record. In these examples, a user, toaccess a record, may be required to authenticate the user's identity,such as by inputting a usemame and/or password, for example, and couldbe required to acknowledge and affirm the sensitive nature of the recordand the user obligations associated with access. As such, the registrysystem may generate an access log that may indicate user identifiers forusers that accessed a given record, a time value associated with accessof the record, and/or what information was displayed and/or manipulatedby the user. The access log may be utilized by the registry system toassist in maintaining confidentiality and/or secrecy of the tradesecret. For example, alerts may be generated and/or sent when a recordis accessed and/or when unusual activity is detected. In other examples,when a user leaves a company, the access record may be utilized todetermine what sensitive information was viewed by the user and whatconfidentiality obligations the departing user should be reminded of. Inother examples, such as when the trade secret is associated with aninsurance policy, the access log may be utilized to satisfy one or moreconditions of the insurance policy, such as, for example, periodicreminders about confidentiality to users that have accessed the record.

The present disclosure provides an overall understanding of theprinciples of the structure, function, manufacture, and use of thesystems and methods disclosed herein. One or more examples of thepresent disclosure are illustrated in the accompanying drawings. Thoseof ordinary skill in the art will understand that the systems andmethods specifically described herein and illustrated in theaccompanying drawings are non-limiting embodiments. The featuresillustrated or described in connection with one embodiment may becombined with the features of other embodiments, including as betweensystems and methods. Such modifications and variations are intended tobe included within the scope of the appended claims.

Additional details are described below with reference to several exampleembodiments.

FIG. 1 illustrates a schematic diagram of an example architecture 100for digital property authentication and management. The architecture 100may include, for example, one or more client-side devices, alsodescribed herein as electronic devices 102, that allow clients toregister and manage their trade secrets or other intangible or digitalassets. The architecture 100 includes a first or trade secret registrysystem 104 associated with a trade secret registry that is remote from,but in communication with, the client-side electronic devices. Thearchitecture 100 further includes a second or distributed ledger system106 that is remote from, but in communication with, the client-sidedevices 102 and the trade secret registry 104. The distributed ledgesystem 106 utilizes blockchain technology to accept entries in a secure,verifiable manner, such as document obfuscation values associated withthe trade secrets or other digital assets being registered by the tradesecret registry. The architecture also has an insurer system 108, whichmay also be described herein as a third remote system associated with aninsurer. The insurer system 108 may utilize information from theregistry system 104 and/or the distributed-ledger system 106 to, forexample, issue insurance policies associated with the trade secretsand/or other digital ssets being registered by the trade secretregistry. Some or all of the devices and systems may be configured tocommunicate with each other via a network 110.

The electronic devices 102 may include components such as, for example,one or more processors 112, one or more network interfaces 114, and/ormemory 116. The memory 116 may include components such as, for example,one or more obfuscation componentobfuscation components 118, a tag-datagenerator 120, a communications component 122, a firewall 124, and/orone or more user interfaces 126. As shown in FIG. 1, the electronicdevices 102 may include, for example, a computing device, a mobilephone, a tablet, a laptop, and/or one or more servers. The components ofthe electronic device 102 will be described below by way of example. Itshould be understood that the example provided herein is illustrative,and should not be considered the exclusive example of the components ofthe electronic device 102.

By way of example, the user interface(s) 126 may include a selectableportion that, when selected, may enable identification of a documentrepresenting a trade secret. For example, the selectable portion and/oranother portion of the user interface 126 may include text requestingthat a user of the user interface 126 select the selectable portion toidentify a document including information to be registered as a tradesecret in association with the trade secret registry. The user mayprovide input to the electronic device 102 indicating the informationand/or document to be registered as a trade secret. The input mayinclude selection of a naming indicator for the document.

The obfuscation component 118 may receive data corresponding to thedocument, such as from one or more databases and/or other storagelocations associated with the electronic device 102 and/or remotestorage accessible by the electronic device 102. The obfuscationcomponent 118 may then generate a document obfuscation valuecorresponding to the document. The obfuscation component 118 may also bedescribed herein as a hash function, and may be configured to map dataof an arbitrary size to data of a fixed size. The document obfuscationvalues may also be described herein as hash codes, digests, and/orhashes. The hash functions may utilize one or more algorithms togenerate document obfuscation values. The algorithms may include, forexample, trivial hash functions, perfect hashing, minimal perfecthashing, hashing uniformly distributed data, hashing data with otherdistributions, hashing variable-length data, special-purpose hashfunctions, rolling hashes, universal hashing, hashing with checksumfunctions, multiplicative hashing, hashing by nonlinear table lookup,efficient hashing of strings, and/or one or more other hashingalgorithms. In general, the obfuscation component 118 may receive, asinput, text data, image data, formatting data, and/or other datacorresponding to the document, and may generate, as output, a documentobfuscation value that corresponds to the input. In examples, theelectronic device 102 may include multiple obfuscation components thateach employ a different hashing algorithm. In these examples, eachobfuscation component may output a different document obfuscation valuefor the same document.

The tag-data generator 120 may be configured to generate tag dataassociated with the document. For example, one or more input fields maybe caused to be displayed via the user interface(s) 126. The inputfields may include a request to “tag” or otherwise provide keywords forthe document. For example, a document that corresponds to source code tooperate a sewing machine may be associated with keywords such as “sourcecode,” “sewing,” “sewing machine,” “version 1.1.20,” etc. A user of theelectronic device 102 may input text corresponding to these tags and thetag-data generator 120 may utilize such input to generate the tag data.Additionally, or alternatively, the tag-data generator 120 mayautomatically generate tag data. For example, the tag-data generator 120may analyze the document to be registered in association with the tradesecret registry to identify keywords associated with the document. Forexample, the tag-data generator 120 may identify one or more fields ofthe document and/or values associated with those fields. By way ofillustration, the tag-data generator 120 may identify a title field, adocument-type field, one or more sections of the document, etc. Thevalues, such as the text data, associated with these fields may beutilized to generate tags. Additionally, or alternatively, text data ofthe document may be analyzed to determine which words are commonly usedin the document, with the user having the ability to review, edit and/ordelete the determined words, e.g., to ensure that particularly sensitiveterms (e.g., a material element of trade secret compound) are notfurther processed. These words may be identified as keywords and may beutilized to generate the tag data.

The communications component 122 may be configured to enablecommunications between the electronic device 102 and the othercomponents of the architecture 100, such as the registry systemregistrysystem 104, the distributed-ledger system 106, and/or the insurer system108. The communications component 122 may further generate data to becommunicated and/or may format already-generated data for transfer toone or more of the remote systems. The communications component 122 mayalso be configured to receive data from one or more of the remotesystems.

The firewall 124 may be configured to receive data from thecommunications component 122 and/or from one or more other components ofthe electronic device 102. The firewall 124 may be described as anetwork security system that may monitor and/or control incoming andoutgoing data based on security rules. The security rules may indicatethat the electronic device 102 is configured to send certain data to theregistry systemregistry system 104, and/or the distributed-ledger system106, and/or the insurer system 108. The security rules may also indicatethat the electronic device 102 is configured to receive certain datafrom the registry system 104, and/or the distributed-ledger system 106,and/or the insurer system 108. By way of example, the security rules mayindicate that the electronic device 102 is permitted to send documentobfuscation values to the registry system 104, but is not permitted tosend documents to the registry system 104. The firewall 124 may beutilized to control the distribution of sensitive information,particularly when the architecture 100 is being utilized to registerconfidential documents with the trade secret registry.

The registry system 104 may include components such as, for example, oneor more processors 128, one or more network interfaces 130, and memory132. The memory 132 may include components such as, for example, one ormore obfuscation components 134, a tag-data generator 136, acommunications component 138, a record generator 140, a trade secretregistry 142, a comparison component 144, a grouping component 146, avaluation component 148, a policy component 150, one or more wizards152, a verification component 154, a trade-secret classifier 156, alinking component 158, an access database 160, an access-controlcomponent 162, and/or a versioning component 164. The components of theregistry system 104 will be described below by way of continued example.It should be understood that the example provided herein isillustrative, and should not be considered the exclusive example of thecomponents of the registry system 104. It should be understood that whena system and/or device is described herein as a “remote system” and/or a“remote device,” the system and/or device may be situated in a locationthat differs from, for example, the electronic device 102.

By way of example, the obfuscation component(s) 134 may perform the sameor similar operations as the obfuscation component(s) 118 of theelectronic device 102. For example, instead of or in addition to the useof obfuscation component(s) 118 by the electronic device 102, theregistry system 104 may generate one or more document obfuscation valuesutilizing the obfuscation component(s) 134. In these examples, theelectronic device 102 may send data corresponding to the documentrepresenting the trade secret to the registry system 104. The registrysystem 104 may receive the data and may utilize the data to generate adocument obfuscation value via the obfuscation component(s) 134. Thedocument obfuscation values may be generated in the same or a similarmanner as the document obfuscation values generated by the obfuscationcomponent(s) 118. In examples, the registry system 104 may includemultiple obfuscation components 134 that each employ a different hashingalgorithm. In these examples, each obfuscation component 134 may outputa different document obfuscation value for the same document. Each ofthese document obfuscation values may be sent to different blockchainsystems for registration, as described elsewhere herein.

In examples, the document may be segmented and each segment may beutilized to generate a document obfuscation value, regardless of wherehashing is performed in the system. For example, two or more portions ofthe document may be identified and/or determined and a documentobfuscation value may be generated for each of the portions. Toillustrate, a document may be segmented into four portions and theobfuscation component(s) 134 may generate a document obfuscation valuefor each of the four portions. The four document obfuscation values maythen be utilized by the obfuscation component(s) 134 to generate adocument obfuscation value for the document.

The tag-data generator 136 may perform the same or similar functions asthe tag-data generator 120 described with respect to the electronicdevice 102. For example, the registry system 104 may receive input dataindicating one or more tags associated with a given trade secret.Additionally, or alternatively, the registry system 104 may generate tagdata utilizing the data representing the document, such as describedabove with respect to the electronic device 102. The registry system 104may also generate tag data reflective of the additional processingperformed by the system. In examples, the tag data may be utilized forsearching functionality. In these examples, a search may be requestedfor one or more records associated with the trade secret registry 142.The search may include text data representing a term to be searched for,and the text data may be utilized by the registry system 104 to searchthrough at least the tag data to find the same or a similar term.Results of the search may be returned to the electronic device 102 fordisplay, such as via the user interface(s) 126. Additionally, oralternatively, the user interface 126 may display the tags as generatedby the tag-data generator 136. The user interface 126 may also display aselectable portion that, when selected, may allow a user to manipulateand/or change the tags.

The communications component 138 may be configured to enablecommunications between the registry system 104 and the other componentsof the architecture 100, such as the electronic device 102, thedistributed-ledger system 106, and/or the insurer system 108. Thecommunications component 138 may further generate data to becommunicated and/or may format already-generated data for transfer toother components of the architecture 100. The communications component138 may also be configured to receive data from one or more of the otherremote systems and/or the electronic device 102.

For example, the communications component 138 may be configured togenerate request data indicating a request to register a trade secret inassociation with a blockchain, such as a blockchain associated with thedistributed-ledger system 106. The request data may be sent to thedistributed-ledger system 106 along with, for example, the documentobfuscation value and/or an identifier of the document and/or the tradesecret, and/or other information associated with the document and/or thetrade secret. The distributed-ledger system 106 may receive the requestdata and the document obfuscation value (or other data) and may registerthe document obfuscation value (or the other data) in association with ablock of the blockchain. The distributed-ledger system 106 may generatea cryptographic document obfuscation value representing the block in theblockchain and/or the distributed-ledger system 106 may generate a timevalue indicating a time and/or day that the document obfuscation value(or the other data) was registered with the blockchain. Thedistributed-ledger system 106 may send the cryptographic documentobfuscation value, the time value, and/or other information (such as ablock number, for example) to the registry system 104 and/or theelectronic device 102.

As used herein, a blockchain is a list and/or ledger of records, alsodescribed as blocks, that are linked using cryptography. A block in theblockchain contains a cryptographic hash of the previous block, a timevalue or timestamp, and, in examples, transaction data. The blockchainmay be utilized to record transactions between two entities and/orsystems. In these examples, the blockchain may be utilized to record thetransaction of registering a trade secret in a trade secret registrybetween the electronic device 102 and the registry system 104. Asdescribed in more detail elsewhere herein, the blockchain may also beutilized to register valuation documentation, insurance policydocuments, and/or other information associated with the trade secretregistry. The blockchain may be managed by a peer-to-peer networkcollectively adhering to a protocol for inter-node communication andvalidating new blocks. Once recorded in a block, the data cannot bealtered without alteration of all subsequent blocks, which would requirea majority of the network to agree upon.

In examples, multiple blockchain systems may be utilized to register thetransaction between the registry system 104 and the electronic device102. For example, the document obfuscation value may be sent to multipleblockchain systems, and each blockchain system may return acryptographic document obfuscation value corresponding to a block intheir respective blockchains. As described more fully below, the recordindicating registration of the trade secret with the trade secretregistry 142 may include the multiple cryptographic document obfuscationvalues and/or other information associated with registration of blocksin the multiple blockchains.

The record generator 140 of the registry system 104 may then generate arecord in the trade secret registry 142. For example, the record mayinclude an identifier of the record, a naming indicator for the tradesecret, a description of the trade secret, a naming indicator of thedocument, one or more tags, a status identifier for the record, thedocument obfuscation value, the cryptographic document obfuscationvalue, the block number, the time value (also described as the blocktimestamp), insurance policy details, valuation details, and/or otherinformation associated with the trade secret. The record may be storedalong with one or more other records in the trade secret registry 142.The registry system 104, in examples, may generate confirmation dataindicating that the record has been generated, and the confirmationdata, along with the record itself, may be sent to the electronic device102 for display via a user interface 126. In examples, auditing ofaccess and/or edit history associated with records may be performed suchthat if a user interacts with the record, data indicating interaction ofthat user with the information associated with the record may besurfaced and/or reported. In addition, audit logs and/or data may beregistered to the distributed-ledger to verify when auditing wasperformed.

In examples, the trade secret registry 142 may be searchable. Forexample, an interface may be generated and configured to allow access toat least a portion of the trade secret registry 142 via the electronicdevice 102 and/or a remote docketing system associated with otherintellectual property assets. Access information, as described morefully herein with respect to the access-control component 162, may besent for accessing the interface. The registry system 104 may receive,such as from the remote docketing system, a request to perform a searchof the trade secret registry 142. In these examples, the request mayinclude text data to be utilized to search the trade secret registry142. The text data may be utilized to identify results of the search andresults data representing the results may be sent to the remotedocketing system and/or the electronic device 102.

The comparison component 144 may be configured to analyze the documentobfuscation values and determine degrees of similarity and/or degrees ordifferences between the document obfuscation values and/or the documentscorresponding to the document obfuscation values. For example, asdescribed above, the obfuscation component(s) 134 may generate documentobfuscation values corresponding to documents representing tradesecrets. Similar documents may have similar document obfuscation values.As such, the comparison component 144 may analyze the documentobfuscation values to determine a degree of similarity between them. Athreshold degree of similarity may be identified and/or determined andthe degree of similarity between document obfuscation values may becompared to the threshold degree of similarity. Document obfuscationvalues with a degree of similarity that meets or exceeds the thresholddegree of similarity may be determined to be similar, while hash-valuepairs that fall below the threshold degree of similarity may bedetermined to be dissimilar. Additionally, document obfuscation valuesmay be segmented and the segments may be compared to determine portionsof the document obfuscation values that are similar and portions thatare not. The number of similar versus dissimilar document obfuscationvalues may be utilized to determine an overall degree of similaritybetween document obfuscation values.

In other examples, the comparison component 144 may associate a featurevector with some or all of the document obfuscation values. The featurevector may correspond to characteristics of the document obfuscationvalue and/or the document. For example, the presence or absence of textdata and/or image data from the document may impact the feature vector.In other examples, the text data and/or image data itself may impact thefeature vector. Other factors such as document length, the entityassociated with the document, the type of information included (e.g.,source code, chemical formula, customer list), creation date,modification date, and/or other metadata may impact the feature vector.By way of example, a feature may be described as an individualmeasurable property or characteristic of a document. A given feature maybe numeric and/or may be considered a string and/or a graphic. A set ofsuch features may be described as a feature vector. As such, similarfeature vectors indicate similar characteristics and/or properties ofthe documents they represent. A similarity and/or popularity score maybe determined for a given pair of feature vectors, with more favorablescores indicating a high degree of similarity between documents.

In other examples, Levenshtein distances may be utilized by thecomparison component 144 to determine a degree of similarity betweentrade secrets. A Levenshtein distance may be determined between twodocument obfuscation values and/or documents. A shorter Levenshteindistance may indicate more similarity than a longer Levenshteindistance. As used herein, a Levenshtein distance, also known as an editdistance, may be described as a string metric for measuring thedifference between two sequences. For example, the Levenshtein distancebetween two words may be considered the minimum number ofsingle-character edits to change one word into the other. As such, theLevenshtein distance between two very similar words would be shorterthan a Levenshtein distance between two very different words. In theseexamples, a Levenshtein distance may be determined between two documentsand/or two document obfuscation values representing those documents,with shorter Levenshtein distances indicating more similarity betweendocuments.

The comparison component 144 may also be configured to determine if ato-be-registered trade secret is unique with respect to other tradesecrets registered in association with the trade secret registry 142.For example, the document obfuscation values and/or documents may beanalyzed as described herein to determine whether a given documentobfuscation value is different from one or more stored documentobfuscation values associated with registered trade secrets. If thedocument obfuscation value is different, then the to-be-registered tradesecret may be identified as or determined to be unique with respect toother trade secrets associated with the trade secret registry 142. Inexamples, determining that the document obfuscation value is differentfrom the stored document obfuscation values may include determining adegree of similarity between the document obfuscation values anddetermining that the degree of similarity does not exceed a thresholddegree of similarity.

The grouping component 146 may be configured to group records and/ordocument obfuscation values corresponding to documents. For example, thegrouping component 146 may utilize the results from the comparisoncomponent 144 to determine whether to group two or more records,document obfuscation values, and/or documents. For example, documentshaving a certain degree of similarity may be grouped together. Groups ofdocuments may also be grouped with other groups of documents based atleast in part on the results from the comparison component 144.Additionally, or alternatively, the grouping component 146 may receivean indication that an identifier of the electronic device 102 and/or theentity is the same as between multiple documents and/or records. Inthese examples, the grouping component 146 may associate the recordshaving the same entity and/or device identifier with each other. Inother examples, the grouping component 146 may group records that haveboth a common entity and/or device identifier and that meet or exceed athreshold degree of similarity.

The valuation component 148 may be configured to identify and/ordetermine a value to associate with a given trade secret. For example,during and/or after registration of a trade secret with the trade secretregistry 142, an option to determine a value for the trade secret orotherwise preserve information related to valuation may be displayed,such as via a user interface 126 of the electronic device 102. One ormore dialog boxes and/or input fields may be caused to be displayed, andthe dialog boxes may request information associated with the tradesecret to aid in valuation of the trade secret. Such information mayinclude, for example, the type of trade secret, an importance of thetrade secret to the entity, entity revenue and profits particularlyincluding revenue and profits attributable to the entity's use of thetrade secret, the development cost of the trade secret information,entity value, date of trade secret creation, expected life of the tradesecret, etc.

Additionally, in examples, the input fields may include a request forsupporting documents that include information that may be relevant tovaluation of the trade secret. In these examples, the user may identifythe supporting documents. A document obfuscation value may be generatedfor a given supporting document and/or the supporting document and/orthe document obfuscation value may be registered in association with theblockchain. The record for the trade secret may include informationassociated with the supporting document, such as the correspondingdocument obfuscation value and/or the cryptographic document obfuscationvalue corresponding to the block in the blockchain where the supportingdocument is registered.

In other examples, the tag data generated as described herein may beutilized to determine some or all of the data described herein as beingutilized to determine a value of a trade secret. For example, the tagdata may be utilized to determine a trade-secret type. Trade secretshaving the same or a similar type may be analyzed to determine a valuefor a trade secret in question. The remote system 104 may utilize someor all of this information to generate a value associated with the tradesecret.

By way of example, a trade secret may be identified and/or determined tobe source code and may be indicated to be extremely valuable to theentity associated with the source code. The input data received from theelectronic device 102 may indicate that the value of the entity is$5,000,000 USD and the yearly revenue for the entity is $1,500,000 USD.The yearly profits attributable to use of the trade secret is $400,000.The development cost of the trade secret was $1,000,000. The expectedlife of the trade secret is 10 years. Additionally, the entity may haveuploaded documents confirming some or all of this information. Based atleast in part on this information, the valuation component 148 maydetermine the value of the trade secret. In examples, a discounted cashflow analysis of the attributable profit streams over the expected lifemay be determined. Comparison may be made to valuations of otherregistered trade secrets, such as other source code identified asimportant and with company statistics that are similar to thoseidentified for the entity. The development cost may be considered. Thesealternative measures may be combined to produce a current and projectedvaluation range. In examples, the valuation component 148 may set one ormore guardrails and/or limits on a value of the trade secret. Forexample, if an entity has a total value of $5,000,000 USD, a limit maybe set that the value of the trade secret cannot exceed $5,000,000 USD.Additionally, or alternatively, data indicating that the trade secrethas been registered with the trade secret registry 142, licensed to athird-party, insured by an insurance carrier, and/or has become morevaluable as reflected in user updates to information associated with thetrade secret since the registry was first established, may be utilizedto influence the valuation of the trade secret.

In still other examples, a quantitative analysis of one or more factorsmay be utilized for valuation. For example, factors such as the relevantindustry, the type of information, the scope of the intellectualproperty, the life span of the intellectual property, thedistinctiveness and/or uniqueness of the intellectual property, theamount of secrecy and/or secrecy measures put in place, thereproducibility of the intellectual property, a likelihood ofmisappropriation, a detectability of the trade secret and/ormisappropriation thereof, and/or an overlap with other intellectualproperty and/or known assets. Still other information such as thegeographic reach of the intellectual property may be utilized. Valuescorresponding to these factors may be identified, determined, and/orgenerated and may be utilized, such as via machine learning algorithms,for example, to determine a value of a trade secret.

The policy component 150 may be configured to assist in the application,underwriting, and provision of one or more insurance policies for agiven trade secret. For example, once registered with the trade secretregistry 142, an option may be presented to gain insurance coverage onthe trade secret. For example, a selectable portion of the userinterface 126 may provide the option to apply for an insurance policy.When selected, the user interface 126 may display one or more dialogboxes and/or input fields configured to receive user input regardingapplication for an insurance policy. This information may include, forexample, information relating to the applicant, a trade-secret type orcategory, a value of the trade secret (either determined from above oridentified by the user), a desired policy period, desired policy limitsand retention, an entity value, a date of creation of the trade secret,and/or a portion enabling uploading of supporting and/or requesteddocumentation. In examples where supporting documentation is provided,the supporting documentation may be registered with the blockchain inthe same or a similar manner as described above with respect to thesupporting document for trade secret valuation.

The policy component 150, and/or the communications component 138, maybe configured to receive input data corresponding to the user input andmay send the input data to the insurer system 108, which is associatedwith an insurer. The insurer system 108 may process the input data and,in examples, underwrite and/or issue a policy insuring the trade secretfrom, for example, misappropriation. In these examples, confirmationdata indicating that the policy has been issued and informationassociated with the policy may be received from the insurer system 108.This information may be incorporated into the record associated with thetrade secret and may be displayed via the user interface 126, inexamples. Some nonlimiting examples of information associated with theinsurance policy may include a policy type, a limit of liability, aretention value, a policy premium, a policy form, a policy number, apolicy period, a sub-limit of liability, and/or a valuation of the tradesecret. Additionally, or alternatively, the information may include apayout value or values associated with amounts of money to be paid tothe entity associated with the trade secret upon the occurrence ofdifferent classes of events including different levels of unauthorizedaccess or use. In these examples, the policy component 150 may receivenoncompliance data indicating that the entity has not complied with acondition of the insurance policy and may cause display of updatedinsurance-policy information including an indicating that curativeaction is required and/or an updated payout value. In these examples,the updated payout value may be less than the original payout value. Asthe condition is met, the payout value may be updated to reflectcompliance with the condition of the insurance policy.

In examples, one or more smart contracts may be utilized in associationwith the policy component 150. For example, the insurance policy may beassociated with a given trade secret using a smart contract associatedwith the blockchain. A smart contract, as described herein, may be acomputer protocol to digitally facilitate, verify, and/or enforce thenegotiation and/or performance of a contract. Transactions involvingsmart contracts may be trackable and irreversible. The smart contractsmay utilize, for example, Byzantine fault tolerant algorithms that mayallow digital security through decentralization of the contract. Thesmart contracts may be initiated, hosted, and/or implemented, at leastin part, by the distributed-ledger system 106 associated with theblockchain. In these examples, the smart contract may indicate acondition for validating an insurance policy, such as management'scontinued investment in threshold level of digital and/or physicalsecurity, and validation data may be received that indicates thecondition has been met. In these examples, the validation data may besent to the distributed-ledger system 106, which may cause the smartcontract to validate the insurance policy.

The wizards 152 as described herein may be a set of dialog boxes and/orinput fields configured to be displayed, such as via the electronicdevice 102. For example, a wizard 152 may be utilized to receive userinput for trade secret valuation determination or support. Additionally,or alternatively, a wizard 152 may be utilized to receive user input forinsurance policy application, underwriting, and provision. In exampleswhere a wizard 152 is utilized for insurance policy provision, thewizard 152 and/or information associated with the wizard 152 may beprovided by and/or may be specific to a given insurer. Additionally, oralternatively, a wizard 152 may be utilized to submit a notice of apotential misappropriation event and/or an insurance claim, as describedmore fully herein.

The verification component 154 may be configured to verify thatinformation included in a particular document has been registered withthe trade secret registry 142. For example, once registered, theverification component 154 may be utilized to determine if and/or verifythat other information, such as information alleged to have beenmisappropriated, matches or is similar to the information included inthe registered document. In these examples, the misappropriatedinformation, e.g., in the form of an accused document, may beidentified, such as via a user interface 126 of the electronic device102, as part of a user verification request. A document obfuscationvalue may be generated for the accused document in the same or a similarmanner as described above with respect to the obfuscation component(s)118, 134. The verification component 154 may be utilized to analyze thedocument obfuscation value for the accused document with respect toother document obfuscation values of registered documents or documentsegments. If the verification component 154 determines that at least oneof the registered document obfuscation values matches the documentobfuscation value for the accused document or document segment, theverification component 154 may determine that the accused document isthe same or similar to the registered document or document segment. Inother examples, the verification component 154 may determine a degree ofsimilarity between the accused document and one or more registereddocuments. Determining the degree of similarity may be performed asdescribed above with respect to the comparison component 144. In theseexamples, the accused document may be determined to be similar to aregistered document when the degree of similarity meets or exceeds athreshold degree of similarity. In still other examples, theverification component 154 may be configured to determine which portionsof an accused document match or are similar to at least one registereddocument. An indication of the matching or similar portions may bedisplayed, such as via the user interface(s) 126. Additionally, ininstances where multiple versions of a document have been registered,the verification component 154 may be configured to determine which ofthe multiple versions is most similar to the accused document, and mayprovide an indication of the version that is most similar.

The trade-secret classifier 156 may be configured to determine a typeand/or classification of a trade secret that is being registered and/orthat has been registered. For example, input data received from theelectronic device 102 indicating one or more properties of a given tradesecret may be utilized by the trade-secret classifier 156 to determinethe type of the trade secret. In other examples, tag data may bereceived, identified, determined, and/or generated as describedelsewhere herein. The tag data may be utilized to determine the type ofthe trade secret. Additionally, or alternatively, the results of thecomparison component 144 may be utilized to determine the type of thetrade secret. For example, matching of similar registered trade secretsmay be utilized to determine a trade-secret type for a given tradesecret. Determining the type of the trade secret may be useful for oneor more of the operations described elsewhere herein, such as forgrouping, valuation, insurance policy provision, wizard display, recordlinking, and document version determination, for example.

The linking component 158 may be configured to associate one record withone or more other records in the trade secret registry 142. For example,when records are determined to be different versions of the samedocument and/or when records are associated with the same entityidentifier, the linking component 158 may be utilized to generate anassociation between those records. Generating the association mayinclude storing data indicating that the records are associated.Generating the association may also, or alternatively, includegenerating a link or other similar functionality that may be displayedalong with a record via the user interface(s) 126. For example, the linkmay correspond to a selectable portion of the user interface(s) 126that, when selected, may cause the linked record and/or a portionthereof to be displayed.

The access database component 160 may be configured to store dataindicating details of access to one or more of the record associatedwith the trade secret registry 142. For example, access-control data maybe stored in association with the registry system 104. Theaccess-control data may indicate who is authorized to view a givenrecord and/or given information associated with a record. In theseexamples, the access-control component 162 may be configured to requirea user, in order to access a record, to authenticate the user'sidentity, such as by inputting a username and/or password, for example.As such, the registry system 104 may generate an access log that mayindicate user identifiers for users that accessed a given record, a timevalue associated with access of the record, and/or what information wasdisplayed and/or manipulated by the user. The access log may be utilizedby the registry system 104 to assist in maintaining confidentialityand/or secrecy of the trade secret. For example, alerts may be generatedand/or sent when a record is accessed and/or when unusual activity isdetected. In other examples, when a user leaves a company, the accessrecord may be utilized to determine what sensitive information wasviewed by the user and what confidentiality obligations the departinguser should be reminded of. In other examples, such as when the tradesecret is associated with an insurance policy, the access log may beutilized to satisfy one or more conditions of the insurance policy, suchas, for example, periodic reminders about confidentiality to users thathave accessed the record. It should be understood that the systemsand/or user interfaces described herein may be utilized to assist inauditing for maintaining trade secret secrecy and/or complying withpolicies and/or rules associated with trade secret maintenance, such asfor insurance policy purposes. Scheduled, periodic, and/or randomreminders may be sent to devices associated with the entity thatregistered a given trade secret. The reminders may request that certaintasks be performed and/or that certain information should be verified tocomply with such policies and/or rules. Additionally, or alternatively,the user interfaces described herein may provide functionality thatallows users of devices display the user interfaces to identify one ormore priority tiers, which may otherwise be described as prioritylevels, to associate with a given trade secret. For example, if a userdesignates a trade secret with a high priority tier, certain actions maybe prohibited, access controls may be more stringent, security measuresmay be more robust, and/or when disclosure of the trade secret is made agiven non-disclosure agreement (which may be a non-form and/ornon-boilerplate non-disclosure agreement) is identified, determined,and/or generated. By way of additional example, if a user designates atrade secret with a low priority tier, certain actions may be enabledthat would not be enabled for a higher tier, access controls may be lessstringent than those for a higher tier, and/or when disclosure of thetrade secret is made, a form and/or standard non-disclosure agreementmay be identified, determined, and/or generated.

In examples where two records are linked, as described more fully withrespect to the linking component 158, the access-control data may beutilized to allow or prohibit access to linked records and/or portionsof the linked records. For example, a given user may have been providedaccess to a first record but not a linked second record. In theseexamples, the first record may be displayed to the user, but when theuser attempts to select a portion of the user interface 126corresponding to a link to the second record, the access-control datamay be utilized to refrain from displaying the second record. In otherexamples, the user may have been authorized to access some informationassociated with the first record but not other information associatedwith the first record. As such, only a portion of the first record maybe displayed to the user, while other portions of the record may beredacted, removed from display, or otherwise not displayed to the user.

The versioning component 164 may be configured to determine that two ormore documents and/or trade secrets are versions of the same documentand/or trade secret. For example, the results from the comparisoncomponent 144, as described more fully above, may be utilized todetermine that two documents are similar in one or more respects but notthe same. The versioning component 164 may further receive, identify,determine, and/or generate information indicating that the two documentsare associated with the same and/or a related entity identifier. Theversioning component 164 may further receive, identify, determine,and/or generate information indicating that the two documents areassociated with the same or a similar trade-secret type. Utilizing someor all of this information, the versioning component 164 may determinethat the two documents are versions of the same document. An indicationof this versioning may be stored with respect to the record(s)associated with the documents and/or a visual indication may bedisplayed via the user interface(s) 126.

The versioning component 164 may also be configured to generate alertsand/or reminders for document versioning. For example, the versioningcomponent 164 may determine that, for a given entity, a version of aparticular trade secret is historically registered at given times and/orwithin given time ranges. If a version is not registered in a way thatcomports with historical trends, an alert and/or reminder forregistering the version of the document may be generated and sent to theelectronic device 102. Additionally, or alternatively, if a given tradesecret is of a type that generally is registered in multiple versions atgiven times and/or within given time ranges, the versioning component164 may determine whether a version has been registered in a way thatcomports with this trend. If a version is not so registered, an alertand/or reminder may be generated and sent.

As shown in FIG. 1, several of the components of the registry system104, the distributed-ledger system 106, and/or the insurer system 108and the associated functionality of those components as described hereinmay be performed by one or more of the other remote systems and/or bythe electronic device 102. Additionally, or alternatively, some or allof the components and/or functionalities associated with the electronicdevice 102 may be performed by the registry system 104, thedistributed-ledger system 106, and/or the insurer system 108.

It should be noted that the exchange of data and/or information asdescribed herein may be performed only in situations where a user hasprovided consent for the exchange of such information. For example, auser may be provided with the opportunity to opt in and/or opt out ofdata exchanges between devices and/or with the remote systems and/or forperformance of the functionalities described herein. Additionally, whenone of the devices is associated with a first user account and anotherof the devices is associated with a second user account, user consentmay be obtained before performing some, any, or all of the operationsand/or processes described herein.

It should be understood that anywhere in this disclosure where the term“trade secret” is used, it should be noted to include not only tradesecrets, but any document and/or data and/or information includingconfidential information, know-how, and other information, and notnecessarily documents, data, and/or information meeting a legaldefinition of the term “trade secret.”

As used herein, a processor, such as processor(s) 112 and/or 128, mayinclude multiple processors and/or a processor having multiple cores.Further, the processors may comprise one or more cores of differenttypes. For example, the processors may include application processorunits, graphic processing units, and so forth. In one implementation,the processor may comprise a microcontroller and/or a microprocessor.The processor(s) 112 and/or 128 may include a graphics processing unit(GPU), a microprocessor, a digital signal processor or other processingunits or components known in the art. Alternatively, or in addition, thefunctionally described herein can be performed, at least in part, by oneor more hardware logic components. For example, and without limitation,illustrative types of hardware logic components that can be used includefield-programmable gate arrays (FPGAs), application-specific integratedcircuits (ASICs), application-specific standard products (ASSPs),system-on-a-chip systems (SOCs), complex programmable logic devices(CPLDs), etc. Additionally, each of the processor(s) 112 and/or 128 maypossess its own local memory, which also may store program components,program data, and/or one or more operating systems.

The memory 116 and/or 132 may include volatile and nonvolatile memory,removable and non-removable media implemented in any method ortechnology for storage of information, such as computer-readableinstructions, data structures, program component, or other data. Suchmemory 116 and/or 132 includes, but is not limited to, RAM, ROM, EEPROM,flash memory or other memory technology, CD-ROM, digital versatile disks(DVD) or other optical storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, RAID storagesystems, or any other medium which can be used to store the desiredinformation and which can be accessed by a computing device. The memory116 and/or 132 may be implemented as computer-readable storage media(“CRSM”), which may be any available physical media accessible by theprocessor(s) 112 and/or 128 to execute instructions stored on the memory116 and/or 132. In one basic implementation, CRSM may include randomaccess memory (“RAM”) and Flash memory. In other implementations, CRSMmay include, but is not limited to, read-only memory (“ROM”),electrically erasable programmable read-only memory (“EEPROM”), or anyother tangible medium which can be used to store the desired informationand which can be accessed by the processor(s).

Further, functional components may be stored in the respective memories,or the same functionality may alternatively be implemented in hardware,firmware, application specific integrated circuits, field programmablegate arrays, or as a system on a chip (SoC). In addition, while notillustrated, each respective memory, such as memory 116 and/or 132,discussed herein may include at least one operating system (OS)component that is configured to manage hardware resource devices such asthe network interface(s), the I/O devices of the respective apparatuses,and so forth, and provide various services to applications or componentsexecuting on the processors. Such OS component may implement a variantof the FreeBSD operating system as promulgated by the FreeBSD Project;other UNIX or UNIX-like variants; a variation of the Linux operatingsystem as promulgated by Linus Torvalds; the FireOS operating systemfrom Amazon. com Inc. of Seattle, Wash., USA; the Windows operatingsystem from Microsoft Corporation of Redmond, Wash., USA; LynxOS aspromulgated by Lynx Software Technologies, Inc. of San Jose, Calif.;Operating System Embedded (Enea OSE) as promulgated by ENEA AB ofSweden; and so forth.

The network interface(s) 114 and/or 130 may enable messages between thecomponents and/or devices shown in architecture 100 and/or with one ormore other remote systems, as well as other networked devices. Suchnetwork interface(s) 114 and/or 130 may include one or more networkinterface controllers (NICs) or other types of transceiver devices tosend and receive messages over the network 110.

For instance, each of the network interface(s) 114 and/or 130 mayinclude a personal area network (PAN) component to enable messages overone or more short-range wireless message channels. For instance, the PANcomponent may enable messages compliant with at least one of thefollowing standards IEEE 802.15.4 (ZigBee), IEEE 802.15.1 (Bluetooth),IEEE 802.11 (WiFi), or any other PAN message protocol. Furthermore, eachof the network interface(s) 114 and/or 130 may include a wide areanetwork (WAN) component to enable message over a wide area network.

In some instances, the registry system 104 may be local to anenvironment associated the electronic device 102. For instance, theremote system 104 may be located within the electronic device 102. Insome instances, some or all of the functionality of the remote system104 may be performed by the electronic device 102. Also, while variouscomponents of the remote system 104 have been labeled and named in thisdisclosure and each component has been described as being configured tocause the processor(s) to perform certain operations, it should beunderstood that the described operations may be performed by some or allof the components and/or other components not specifically illustrated.

FIG. 2 illustrates an example user interface 202 displaying trade secretregistration functionality in accordance with a digital propertyauthentication and management system. The user interface 202 may bedisplayed on a display of an electronic device, such as the electronicdevice 102 as described with respect to FIG. 1. The user interface 202may be the same as or similar to the user interface(s) 126 as describedwith respect to FIG. 1. FIG. 2 illustrates a progression, from left toright and top to bottom, of information displayed on and/or interactionswith the user interface 202.

For example, the user interface 202, at step 1, may include a firstselectable portion 204 indicating an option to register a trade secretwith a trade secret registry. The user interface 202 may also include asecond selectable portion 206 indicating an option to manage registeredtrade secrets, and/or a third selectable portion 208 indicating anoption to verify that a document has been registered in association withthe trade secret registry. To illustrate the use and functionality ofthe user interface 202, a user may provide input indicating selection ofthe first selectable portion 204.

Selection of the first selectable portion 204 may cause the userinterface 202 to display, at step 2, a fourth selectable portion 210indicating an option to identify a document representing a trade secretto be registered with the trade secret registry. Identification of thedocument may include input such as a naming indicator for the documentand/or selection of a document from a database of an electronic devicedisplaying the user interface 202, for example. The document may beidentified and the electronic device may cause a document obfuscationvalue to be generated corresponding to the document. For example, aobfuscation component may receive data corresponding to the document,such as from one or more databases and/or other storage locationsassociated with the electronic device and/or remote storage accessibleby the electronic device. The obfuscation component may then generate adocument obfuscation value corresponding to the document. In general,the obfuscation component may receive, as input, text data, image data,formatting data, and/or other data corresponding to the document, andmay generate, as output, a document obfuscation value that correspondsto the input. In examples, the electronic device may include multipleobfuscation components that each employ a different hashing algorithm.In these examples, each obfuscation component may output a differentdocument obfuscation value for the same document.

At step 3, the user interface 202 may include a naming indicator 212 forthe document. The user interface 202 may also include the documentobfuscation value 214 as generated based at least in part on thedocument. As shown in FIG. 2, the naming indicator 212 for the documentis “Document 1,” and the document obfuscation value 214 is“0xaafdee662b084f7378f1ad91bfe08bdb34de 61e801efb61103043fc62bd8963f,”by way of example.

At step 4, the user interface 202 may include one or more dialog boxesand/or input fields 216 associated with the trade secret. The inputfields 216 may include text requesting information from the userregarding the trade secret. As shown in FIG. 2, by way of example, theinput fields 216 may request information such as a trade secret name, adescription of the trade secret, and/or one or more tags for the tradesecret. For example, a document that corresponds to source code tooperate a sewing machine may be associated with keywords such as “sourcecode,” “sewing,” “sewing machine,” “version 1.1.20,” etc. A user of theelectronic device may input text corresponding to these tags and atag-data generator may utilize such input to generate the tag data.Additionally, or alternatively, the tag-data generator may automaticallygenerate tag data. For example, the tag-data generator may analyze thedocument to be registered in association with the trade secret registryto identify keywords associated with the document. For example, thetag-data generator may identify one or more fields of the documentand/or values associated with those fields. By way of illustration, thetag-data generator may identify a title field, a document-type field,one or more sections of the document, etc. The values, such as the textdata, associated with these fields may be utilized to generate tags.Additionally, or alternatively, text data of the document may beanalyzed to determine which words are commonly used in the document.These words may be identified as keywords and may be utilized togenerate the tag data.

At step 5, the user interface 202 may display text indicating a statusof the registration process and/or a description of operations beingperformed, such as by a remote system associated with the trade secretregistry and/or a remote system associated with a blockchain. Forexample, the text may state that the transaction is pending and maystate that the trade secret and/or the document obfuscation value isbeing submitted to the blockchain. While this text is being displayed, acommunications component may generate request data indicating a requestto register a trade secret in association with the blockchain. Therequest data may be sent to the remote system associated with theblockchain along with, for example, the document obfuscation valueand/or an identifier of the document and/or the trade secret, and/orother information associated with the document and/or the trade secret.The remote system may receive the request data and the documentobfuscation value (or other data) and may register the documentobfuscation value (or the other data) in association with a block of theblockchain. The remote system may generate a cryptographic documentobfuscation value representing the block in the blockchain and/or theremote system may generate a time value indicating a time and/or daythat the document obfuscation value (or the other data) was registeredwith the blockchain. The remote system may send the cryptographicdocument obfuscation value, the time value, and/or other information(such as a block number, for example) to the remote system associatedwith the trade secret registry.

In examples, multiple blockchain systems may be utilized to register thetransaction between the trade secret registry system and the electronicdevice. For example, the document obfuscation value may be sent tomultiple blockchain systems, and each blockchain system may return acryptographic document obfuscation value corresponding to a block intheir respective blockchains. As described more fully below, the recordindicating registration of the trade secret with the trade secretregistry may include the multiple cryptographic document obfuscationvalues and/or other information associated with registration of blocksin the multiple blockchains.

At step 6, the user interface 202 may display a record indicating thatthe trade secret has been registered with the trade secret registry. Therecord may include a record identifier 218, trade-secret details 220,and/or transaction details 222. The record identifier 218 may includenumbers and/or letters that identify the record with respect to thetrade secret registry. The trade-secret details 220 may, for example,include a naming indicator for the trade secret, a description of thetrade secret, a naming indicator for the document representing the tradesecret, and/or the tags generated as described elsewhere herein. Thetransaction details 222 may include a status of the registration withthe trade secret registry, the document obfuscation value, a blocknumber associated with the block at which the trade secret is registeredwith the blockchain, the cryptographic document obfuscation value (alsodescribed as the block document obfuscation value), and/or the blocktimestamp. Other information that may be included in the record anddisplayed with respect to the user interface 202 may include insurancepolicy details, valuation details, and/or other information associatedwith the trade secret, as described more fully elsewhere herein.

The record may be generated by a record generator of the remote systemassociated with the trade secret registry. The record may be storedalong with one or more other records in the trade secret registry. Theremote system, in examples, may generate confirmation data indicatingthat the record has been generated, and the confirmation data may besent to the electronic device for display via a user interface 202.

FIG. 3 illustrates an example user interface 302 displaying trade secretmaintenance functionality in accordance with a digital propertyauthentication and management system. The user interface 302 may bedisplayed on a display of an electronic device, such as the electronicdevice 102 as described with respect to FIG. 1. The user interface 302may be the same as or similar to the user interface(s) 126 as describedwith respect to FIG. 1. FIG. 3 illustrates a progression, from left toright and top to bottom, of information displayed on and/or interactionswith the user interface 302.

For example, the user interface 302, at step 1, may include a firstselectable portion 304 indicating an option to register a trade secretwith a trade secret registry. The user interface 302 may also include asecond selectable portion 306 indicating an option to manage registeredtrade secrets, and/or a third selectable portion 308 indicating anoption to verify that a document has been registered in association withthe trade secret registry. To illustrate the use and functionality ofthe user interface 302, a user may provide input indicating selection ofthe second selectable portion 306. It should be understood that, inexamples, the first, second, and third selectable portions 304, 306, 308of the user interface 302 may be the same as or similar to (and mayfunction similarity to) the first, second, and third selectable portions204, 206, 208 of the user interface 202 described with respect to FIG.2.

Selection of the second selectable portion 306 may cause the userinterface 302 to display, at step 2, information associated with tradesecrets that have been registered in association with the trade secretregistry. In examples, trade-secret indicators 310 may be displayed. Thetrade-secret indicators 310 may include information describing and/orsummarizing a given trade secret. As shown in FIG. 3, by way of example,the information may include a name of a trade secret, a date on whichthe trade secret was registered in association with the trade secretregistry, and/or tags associated with the trade secret. In this way, thetrade-secret indicators 310 provide an indication of the trade secretsassociated with the trade secret registry without providing, inexamples, all of the information of each record of the trade secrets. Inexamples, the trade-secret indicators 310 may be limited to only thosetrade secrets associated with a given entity and/or entity identifier.Additionally, or alternatively, the trade-secret indicators 310 may belimited to only those trade secrets to which a user logged in withcertain access credentials has authorization to view.

In examples, the trade-secret indicators 310 may be selectable, and,when selected, may cause the record associated with that trade-secretindicator 310 to be displayed at step 3. As shown in FIG. 3, a user mayprovide input corresponding to selection of “Trade Secret 1.” Selectionof the trade-secret indicator may cause display, at step 3, of therecord associated with “Trade Secret 1.” As shown in FIG. 3, the recordmay include the same or similar information as the record described withrespect to FIG. 2, including a record identifier, trade-secret details,and/or transaction details.

In addition to the details displayed as described above, thetrade-secret indicators 310 and/or the records may include a link 312 toone or more other records associated with the trade secret registry. Forexample, a linking component may be configured to associate one recordwith one or more other records in the trade secret registry. Forexample, when records are determined to be different versions of thesame document and/or when records are associated with the same entityidentifier, the linking component may be utilized to generate anassociation between those records. Generating the association mayinclude storing data indicating that the records are associated.Generating the association may also, or alternatively, includegenerating a link 312 or other similar functionality that may bedisplayed along with a record via the user interface 302. For example,the link 312 may correspond to a selectable portion of the userinterface 302 that, when selected, may cause the linked record and/or aportion thereof to be displayed.

FIG. 4 illustrates an example user interface 402 displaying trade secretverification functionality in accordance with a digital propertyauthentication and management system. The user interface 402 may bedisplayed on a display of an electronic device, such as the electronicdevice 102 as described with respect to FIG. 1. The user interface 402may be the same as or similar to the user interface(s) 126 as describedwith respect to FIG. 1. FIG. 4 illustrates a progression, from left toright, of information displayed on and/or interactions with the userinterface 402.

For example, the user interface 402, at step 1, may include a firstselectable portion 404 indicating an option to register a trade secretwith a trade secret registry. The user interface 402 may also include asecond selectable portion 406 indicating an option to manage registeredtrade secrets, and/or a third selectable portion 408 indicating anoption to verify that a document has been registered in association withthe trade secret registry. To illustrate the use and functionality ofthe user interface 402, a user may provide input indicating selection ofthe third selectable portion 306.

Selection of the third selectable portion 306 may cause the userinterface 302 to display, at step 2, a fourth selectable portion 410indicating an option to identify a document accused, for example, ofbeing misappropriated. In these examples, the document may be obtainedfrom a third party that may be accused of misappropriation or otherwiseobtaining the trade secret without permission. Identification of theaccused document may include input such as a naming indicator for thedocument and/or selection of a document from a database of an electronicdevice displaying the user interface 402, for example. The document maybe identified and the electronic device may cause a document obfuscationvalue to be generated corresponding to the document. For example, aobfuscation component may receive data corresponding to the document,such as from one or more databases and/or other storage locationsassociated with the electronic device and/or remote storage accessibleby the electronic device. The obfuscation component may then generate adocument obfuscation value corresponding to the document. In general,the obfuscation component may receive, as input, text data, image data,video data, formatting data, and/or any other data corresponding to thedocument and/or file representing the trade secret, and may generate, asoutput, a document obfuscation value that corresponds to the input. Inexamples, the electronic device may include multiple obfuscationcomponents that each employ a different hashing algorithm. In theseexamples, each obfuscation component may output a different documentobfuscation value for the same document.

At step 3, the user interface 402 may display a verification status 412,a similarity indicator 414, and/or an identifier 416 of the registeredtrade secret that was determined to match and/or be similar to theaccused document. For example, a verification component may beconfigured to verify that a particular document has been registered withthe trade secret registry. For example, once registered, theverification component may be utilized to determine if and/or verifythat another document, such as a document accused to have beenmisappropriated, matches or is similar to the registered document. Theverification component may be utilized to analyze the documentobfuscation value for the accused document with respect to otherdocument obfuscation values of registered documents. If the verificationcomponent determines that at least one of the registered documentobfuscation values matches the document obfuscation value for theaccused document, the verification component may determine that theaccused document is the same or similar to the registered document. Inother examples, the verification component may determine a degree ofsimilarity between the accused document and one or more registereddocuments.

Determining the degree of similarity may be performed as described abovewith respect to the comparison component 144 of FIG. 1. In theseexamples, the accused document may be determined to be similar to aregistered document when the degree of similarity meets or exceeds athreshold degree of similarity. In still other examples, theverification component may be configured to determine which portions ofan accused document match or are similar to at least one registereddocument. An indication of the matching or similar portions may bedisplayed, such as via the user interface(s) 402. Additionally, ininstances where multiple versions of a document have been registered,the verification component may be configured to determine which of themultiple versions is most similar to the accused document, and mayprovide an indication of the version that is most similar.

As shown by way of example in FIG. 4, the verification status 412 is“document verified,” indicating that the accused document matches or issimilar to at least one registered trade secret. The similarityindicator 414 is “97% match with a registered document,” indicating thatthe accused document is 97% similar to at least one of the registereddocuments. It should be understood that the particular wording of theverification status 412 and/or the similarity indicator 414 is providedby way of example, and not as a limitation. Other forms of verificationstatus and/or similarity indicators may be provided. Additionally, whilesimilarity is expressed in FIG. 4 as a percentage, other forms ofdescribing similarity are included in this disclosure. Additionally, theidentifier 416 of the registered trade secret is “Name: Trade Secret 1.”This may provide an indication to the user of the registered tradesecret that is similar to the accused document.

In examples, the user interface 402 may display dialog boxes and/orinput fields including text associated with submitting a claim forinsurance coverage in association with an insurance policy for the tradesecret. In these examples, given that an allegation of trade secretmisappropriation, or other legal claim, may exist in light of thesimilarity between the accused document and the registered trade secret,one or more wizards may be initiated to assist in filing a claim forinsurance coverage. Input data may be received representing responses tothe dialog boxes, and based at least in part on receiving the inputdata, the input data may be formatted and/or sent to a remote systemassociated with an insurer indicating that a claim is to be filed and/ornotifying the insurer of the potential misappropriation and/or otherlegal action.

FIG. 5 illustrates an example user interface 502 displaying insurancepolicy functionality in accordance with a digital propertyauthentication and management system. The user interface 502 may bedisplayed on a display of an electronic device, such as the electronicdevice 102 as described with respect to FIG. 1. The user interface 502may be the same as or similar to the user interface(s) 126 as describedwith respect to FIG. 1. FIG. 5 illustrates a progression, from left toright, of information displayed on and/or interactions with the userinterface 502.

At step 1, the user interface 502 may display a record indicating atrade secret that has been registered with the trade secret registry.The record may include a record identifier 504, trade-secret details506, and/or transaction details 508. The record identifier 504 mayinclude numbers and/or letters that identify the record with respect tothe trade secret registry. The trade-secret details 506 may, forexample, include a naming indicator for the trade secret, a descriptionof the trade secret, a naming indicator for the document representingthe trade secret, and/or the tags generated as described elsewhereherein. The transaction details 508 may include a status of theregistration with the trade secret registry, the document obfuscationvalue, a block number associated with the block at which the tradesecret is registered with the blockchain, the cryptographic documentobfuscation value (also described as the block document obfuscationvalue), and/or the block timestamp. Additionally, the user interface 502may include a selectable portion 510 indicating an option to apply forand/or acquire an insurance policy associated with the trade secret.

At step 2, based at least in part on selection of the selectable portion510, the user interface 502 may display a sequence of dialog boxesand/or input fields 512 requesting information associated with applyingfor an insurance policy. For example, a policy component may beconfigured to assist in the provision of one or more insurance policiesfor a given trade secret. The information requested via the input fields512 may include, for example, a trade-secret type or category, a valueof the trade secret (either determined from above or identified by theuser), a policy period, an entity value, a date of creation of the tradesecret, and/or a portion enabling uploading of supporting and/orrequested documentation. In examples where supporting documentation isprovided, the supporting documentation may be registered with theblockchain in the same or a similar manner as described above withrespect to the supporting document for trade secret valuation.

The policy component, and/or another component of the electronic deviceand/or the trade secret registry system, may be configured to receiveinput data corresponding to the user input and may send the input datato the remote system associated with the insurer. The remote system mayprocess the input data and, in examples, issue a policy insuring thetrade secret from, for example, misappropriation. In these examples,confirmation data indicating that the policy has been issued andinformation associated with the policy may be received from the remotesystem. This information, described as policy details 514, may beincorporated into the record associated with the trade secret and may bedisplayed, at step 3, via the user interface 502, in examples. Somenonlimiting examples of policy details 514 may include a policy type, alimit of liability, a retention value, a policy premium, a policy form,a policy number, a policy period, a sub-limit of liability, and/or avaluation of the trade secret. Additionally, or alternatively, thepolicy details 514 may include a payout value associated with an amountof money to be paid to the entity associated with the trade secret uponthe occurrence of an event. In these examples, the policy component mayreceive compliance data indicating that the entity has not complied witha condition of the insurance policy and may cause display of updatedinsurance-policy information including an updated payout value. In theseexamples, the updated payout value may be less than the original payoutvalue. As the condition is met, the payout value may be updated toreflect compliance with the condition of the insurance policy.

In examples, one or more smart contracts may be utilized in associationwith the policy component. For example, the insurance policy may beassociated with a given trade secret using a smart contract associatedwith the blockchain. A smart contract, as described herein, may be acomputer protocol to digitally facilitate, verify, and/or enforce thenegotiation and/or performance of a contract. Transactions involvingsmart contracts may be trackable and irreversible. The smart contractsmay utilize, for example, Byzantine fault tolerant algorithms that mayallow digital security through decentralization of the contract. Thesmart contracts may be initiated, hosted, and/or implemented, at leastin part, by the remote system associated with the blockchain. In theseexamples, the smart contract may indicate a condition for validating aninsurance policy, and validation data may be received that indicates thecondition has been met. In these examples, the validation data may besent to the distributed-ledger system 106, which may cause the smartcontract to validate the insurance policy.

FIG. 6 illustrates an example user interface 602 displaying valuationfunctionality in accordance with a digital property authentication andmanagement system. The user interface 602 may be displayed on a displayof an electronic device, such as the electronic device 102 as describedwith respect to FIG. 1. The user interface 602 may be the same as orsimilar to the user interface(s) 126 as described with respect toFIG. 1. FIG. 6 illustrates a progression, from left to right, ofinformation displayed on and/or interactions with the user interface602.

At step 1, the user interface 602 may display a record indicating atrade secret that has been registered with the trade secret registry.The record may include a record identifier 604, trade-secret details606, and/or transaction details 608. The record identifier 604 mayinclude numbers and/or letters that identify the record with respect tothe trade secret registry. The trade-secret details 606 may, forexample, include a naming indicator for the trade secret, a descriptionof the trade secret, a naming indicator for the document representingthe trade secret, and/or the tags generated as described elsewhereherein. The transaction details 608 may include a status of theregistration with the trade secret registry, the document obfuscationvalue, a block number associated with the block at which the tradesecret is registered with the blockchain, the cryptographic documentobfuscation value (also described as the block document obfuscationvalue), and/or the block timestamp. Additionally, the user interface 602may include a selectable portion 610 indicating an option to determine avalue for the trade secret.

At step 2, based at least in part on selection of the selectable portion610, the user interface 602 may display a sequence of dialog boxesand/or input fields 612 requesting information associated withdetermining a value of the trade secret. For example, a valuationcomponent may be configured to identify and/or determine a value toassociate with a given trade secret. The information requested by theinput fields 612 may include, for example, the type of trade secret, animportance of the trade secret to the entity, entity revenue, entityvalue, date of trade secret creation, etc.

Additionally, in examples, the input fields 612 may include a requestfor supporting documents that include information that may be relevantto valuation of the trade secret. In these examples, the user mayidentify the supporting documents. A document obfuscation value may begenerated for a given supporting document and/or the supporting documentand/or the document obfuscation value may be registered in associationwith the blockchain. The record for the trade secret may includeinformation associated with the supporting document, such as thecorresponding document obfuscation value and/or the cryptographicdocument obfuscation value corresponding to the block in the blockchainwhere the supporting document is registered.

In other examples, tag data generated as described herein may beutilized to determine some or all of the data described herein as beingutilized to determine a value of a trade secret. For example, the tagdata may be utilized to determine a trade-secret type. Trade secretshaving the same or a similar type may be analyzed to determine a valuefor a trade secret in question. The remote system 104 may utilize someor all of this information to generate a value associated with the tradesecret.

By way of example, a trade secret may be identified and/or determined tobe source code and may be indicated to be extremely valuable to theentity associated with the source code. The input data received from theelectronic device may indicate that the value of the entity is$5,000,000 USD and the yearly revenue for the entity is $350,000 USD.Additionally, the entity may have uploaded documents confirming some orall of this information. Based at least in part on this information, thevaluation component may determine the value of the trade secret. Inexamples, comparison may be made between other registered trade secrets,such as other source code identified as important and with companystatistics that are similar to those identified for the entity. Inexamples, the valuation component may set one or more guardrails and/orlimits on a value of the trade secret. For example, if an entity has atotal value of $5,000,000 USD, a limit may be set that the value of thetrade secret cannot exceed $5,000,000 USD. Additionally, oralternatively, data indicating that the trade secret has been registeredwith the trade secret registry, and/or an amount of time since the tradesecret was registered, may be utilized to influence the valuation of thetrade secret.

Confirmation data indicating that the value has been determined andinformation associated with the valuation may be received from theremote system. This information, described as valuation details 614, maybe incorporated into the record associated with the trade secret and maybe displayed, at step 3, via the user interface 602, in examples. Somenonlimiting examples of valuation details 614 may include the value, atrade-secret type, a trade-secret creation date, an entity value, anentity revenue value, and/or one or more selectable links that, whenselected, may cause display of supporting documentation, if any,provided for valuation purposes.

FIG. 7 illustrates an example user interface 702 displaying accesscontrol functionality in accordance with a digital propertyauthentication and management system. The user interface 702 may bedisplayed on a display of an electronic device, such as the electronicdevice 102 as described with respect to FIG. 1. The user interface 702may be the same as or similar to the user interface(s) 126 as describedwith respect to FIG. 1. FIG. 7 illustrates a progression, from left toright and top to bottom, of information displayed on and/or interactionswith the user interface 702.

At step 1, the user interface 702 may include an authentication screenrequesting user input to authenticate access to records associated withthe trade secret registry. For example, a usemame 704 and a password 706may be requested. A user may provide input and corresponding input datamay be analyzed by the electronic device displaying the user interface702 and/or a remote system associated with the trade secret registry.

Upon authentication of the user input, at step 2, the user interface 702may include a first selectable portion 708 indicating an option toregister a trade secret with a trade secret registry. The user interface702 may also include a second selectable portion 710 indicating anoption to manage registered trade secrets, and/or a third selectableportion 712 indicating an option to verify that a document has beenregistered in association with the trade secret registry. To illustratethe use and functionality of the user interface 702, a user may provideinput indicating selection of the second selectable portion 710. Itshould be understood that, in examples, the first, second, and thirdselectable portions 708, 710, 712 of the user interface 702 may be thesame as or similar to (and may function similarity to) the first,second, and third selectable portions 204, 206, 208 of the userinterface 202 described with respect to FIG. 2.

Selection of the second selectable portion 710 may cause the userinterface 702 to display, at step 3, information associated with tradesecrets that have been registered in association with the trade secretregistry. In examples, trade-secret indicators 714 may be displayed. Thetrade-secret indicators 714 may include information describing and/orsummarizing a given trade secret. As shown in FIG. 7, by way of example,the information may include a name of a trade secret, a date on whichthe trade secret was registered in association with the trade secretregistry, and/or tags associated with the trade secret. In this way, thetrade-secret indicators 714 provide an indication of the trade secretsassociated with the trade secret registry without providing, inexamples, all of the information of each record of the trade secrets. Inexamples, the trade-secret indicators 714 may be limited to only thosetrade secrets associated with a given entity and/or entity identifier.Additionally, or alternatively, the trade-secret indicators 714 may belimited to only those trade secrets to which a user logged in withcertain access credentials has authorization to view.

In examples, the trade-secret indicators 714 may be selectable, and,when selected, may cause the record associated with that trade-secretindicator 714 to be displayed at step 4. As shown in FIG. 7, a user mayprovide input corresponding to selection of “Trade Secret 1.” Selectionof the trade-secret indicator may cause display, at step 4, of therecord associated with “Trade Secret 1.” As shown in FIG. 7, the recordmay include the same or similar information as the record described withrespect to FIG. 2, including a record identifier, trade-secret details,and/or transaction details.

As shown in step 4, based at least in part on access-control dataassociated with the authentication information provided by the user toaccess the system, one or more access controls may be implemented torestrict access to a record and/or to a portion of a record. Forexample, as shown in FIG. 7, the access-control data associated with theuser viewing the record indicates that the user has authorization toview the record identifier, trade-secret details, and transactiondetails, but does not have access to certain valuation details. Forexample, the access-control data indicates that access is authorized forthe trade-secret type and the creation date, but access is prohibitedfor the value, the entity value, and/or the revenue value. As such, anentity associated with the system may set access authorizations anddetermine, for given individuals, what information will be available.Additionally, or alternatively, the access-control data may indicatethat a given individual is authorized to utilize certain functionalityof the trade secret registry but is prohibited from utilizing otherfunctionality. For example, the individual may be authorized to viewcertain records and/or information associated with records but may beprohibited from manipulating and/or changing a record, such as adding,removing, and/or changing tags.

At step 5, the user interface may again display the trade-secretindicators 714. In this example, the access-control data may indicatethat access to “Trade Secret 1” is authorized while access to “TradeSecret 2” is prohibited. As such, upon selection of the trade-secretindicator 714 corresponding to “Trade Secret 2,” at step 6, the userinterface 702 may display information indicating that access isprohibited or otherwise denied. Additionally, in instances where recordshave been linked as described elsewhere herein, and a link has beenprovided between records, upon selection of the link, the access-controldata may be utilized to determine whether to display the linked record.

FIGS. 8-23 illustrate processes for digital property authentication andmanagement. The processes described herein are illustrated ascollections of blocks in logical flow diagrams, which represent asequence of operations, some or all of which may be implemented inhardware, software or a combination thereof. In the context of software,the blocks may represent computer-executable instructions stored on oneor more computer-readable media that, when executed by one or moreprocessors, program the processors to perform the recited operations.Generally, computer-executable instructions include routines, programs,objects, components, data structures and the like that performparticular functions or implement particular data types. The order inwhich the blocks are described should not be construed as a limitation,unless specifically noted. Any number of the described blocks may becombined in any order and/or in parallel to implement the process, oralternative processes, and not all of the blocks need be executed. Fordiscussion purposes, the processes are described with reference to theenvironments, architectures and systems described in the examplesherein, such as, for example those described with respect to FIGS. 1-7,although the processes may be implemented in a wide variety of otherenvironments, architectures and systems.

FIG. 8 illustrates a flow diagram of an example process 800 for tradesecret registration in accordance with a digital property authenticationand management system. The order in which the operations or steps aredescribed is not intended to be construed as a limitation, and anynumber of the described operations may be combined in any order and/orin parallel to implement process 800. The operations described withrespect to the process 800 are described as being performed by theelectronic device, and/or the registry system associated with the tradesecret registry, and/or a distributed-ledger system associated with ablockchain. However, it should be understood that some or all of theseoperations may be performed by some or all of components, devices,and/or systems described herein.

At block 802, the process 800 may include the electronic devicereceiving a document representing a trade secret. By way of example, auser interface may include a selectable portion that, when selected, mayenable identification of a document representing a trade secret. Forexample, the selectable portion and/or another portion of the userinterface may include text requesting that a user of the user interfaceselect the selectable portion to identify a document to be registered asa trade secret in association with the trade secret registry. The usermay provide input to the electronic device indicating the document to beregistered as a trade secret. The input may include selection of anaming indicator for the document.

At block 804, the process 800 may include the electronic devicegenerating a document obfuscation value corresponding to the document.For example, a obfuscation component may receive data corresponding tothe document, such as from one or more databases and/or other storagelocations associated with the electronic device and/or remote storageaccessible by the electronic device. The obfuscation component may thengenerate a document obfuscation value corresponding to the document. Ingeneral, the obfuscation component may receive, as input, text data,image data, formatting data, and/or other data corresponding to thedocument, and may generate, as output, a document obfuscation value thatcorresponds to the input. In examples, the electronic device may includemultiple obfuscation components that each employ a different hashingalgorithm. In these examples, each obfuscation component may output adifferent document obfuscation value for the same document.

At block 806, the process 800 may include the registry system receivingthe document obfuscation value and request data indicating a request toregister the trade secret with the trade secret registry. For example,the document obfuscation value may be received from the electronicdevice, such as via a firewall. Additionally, the electronic device mayhave generated and sent request data indicating a request to registerthe trade secret with the trade secret registry.

Based at least in part on receiving the document obfuscation valueand/or the request data, a communications component of the registrysystem may be configured to generate request data indicating a requestto register a trade secret in association with a blockchain, such as ablockchain associated with the distributed-ledger system. The requestdata may be sent to the distributed-ledger system along with, forexample, the document obfuscation value and/or an identifier of thedocument and/or the trade secret, and/or other information associatedwith the document and/or the trade secret.

At block 808, the process 800 may include the distributed-ledger systemgenerating a cryptographic document obfuscation value corresponding to ablock in the blockchain. For example, the distributed-ledger system mayreceive the request data and the document obfuscation value (or otherdata) and may register the document obfuscation value (or the otherdata) in association with a block of the blockchain. Thedistributed-ledger system may generate a cryptographic documentobfuscation value representing the block in the blockchain and/or thedistributed-ledger system may generate a time value indicating a timeand/or day that the document obfuscation value (or the other data) wasregistered with the blockchain. The distributed-ledger system may sendthe cryptographic document obfuscation value, the time value, and/orother information (such as a block number, for example) to the registrysystem and/or the electronic device. At block 810, the process 800 mayinclude the registry system receiving the cryptographic documentobfuscation value from the distributed-ledger system.

At block 812, the process 800 may include the registry system generatinga record corresponding to the trade secret in the trade secret registry.For example, a record generator of the registry system may then generatea record in the trade secret registry. For example, the record mayinclude an identifier of the record, a naming indicator for the tradesecret, a description of the trade secret, a naming indicator of thedocument, one or more tags, a status identifier for the record, thedocument obfuscation value, the cryptographic document obfuscationvalue, the block number, the time value (also described as the blocktimestamp), insurance policy details, valuation details, and/or otherinformation associated with the trade secret. The record may be storedalong with one or more other records in the trade secret registry.

At block 814, the process 800 may include the registry system maygenerate tag data associated with the document. For example, a tag-datagenerator may be configured to generate tag data associated with thedocument. In examples, one or more input fields may be caused to bedisplayed via a user interface of the electronic device. The inputfields may include a request to “tag” or otherwise provide keywords forthe document. For example, a document that corresponds to source code tooperate a sewing machine may be associated with keywords such as “sourcecode,” “sewing,” “sewing machine,” “version 1.1.20,” etc. A user of theelectronic device may input text corresponding to these tags and thetag-data generator may utilize such input to generate the tag data.Additionally, or alternatively, the tag-data generator may automaticallygenerate tag data. For example, the tag-data generator may analyze thedocument to be registered in association with the trade secret registryto identify keywords associated with the document. For example, thetag-data generator may identify one or more fields of the documentand/or values associated with those fields. By way of illustration, thetag-data generator may identify a title field, a document-type field,one or more sections of the document, etc. The values, such as the textdata, associated with these fields may be utilized to generate tags.Additionally, or alternatively, text data of the document may beanalyzed to determine which words are commonly used in the document.These words may be identified as keywords and may be utilized togenerate the tag data.

At block 816, the process 800 may include the registry systemassociating the trade secret with one or more other trade secretsregistered with respect to the trade secret registry. For example, alinking component may be configured to associate one record with one ormore other records in the trade secret registry. When records aredetermined to be different versions of the same document and/or whenrecords are associated with the same entity identifier, the linkingcomponent may be utilized to generate an association between thoserecords. Generating the association may include storing data indicatingthat the records are associated. Generating the association may also, oralternatively, include generating a link or other similar functionalitythat may be displayed along with a record via the user interface. Forexample, the link may correspond to a selectable portion of the userinterface that, when selected, may cause the linked record and/or aportion thereof to be displayed.

At block 818, the process 800 may include the electronic devicereceiving confirmation data indicating the record has been generated.The registry system, in examples, may generate confirmation dataindicating that the record has been generated, and the confirmation datamay be sent to the electronic device.

At block 820, the process 800 may include the electronic device causingdisplay of information associated with the record. Display ofinformation associated with the record may include information such asthat described herein, for example, with respect to FIGS. 1-7.

FIG. 9 illustrates a flow diagram of an example process 900 for tradesecret verification in accordance with a digital property authenticationand management system. The order in which the operations or steps aredescribed is not intended to be construed as a limitation, and anynumber of the described operations may be combined in any order and/orin parallel to implement process 900. The operations described withrespect to the process 900 are described as being performed by theelectronic device, and/or the registry system associated with the tradesecret registry, and/or a distributed-ledger system associated with ablockchain. However, it should be understood that some or all of theseoperations may be performed by some or all of components, devices,and/or systems described herein.

At block 902, the process 900 may include the electronic devicereceiving an accused document and/or an identifier of the accuseddocument. For example, a selectable portion of a user interface may bedisplayed on the electronic device indicating an option to identify adocument accused, for example, of being misappropriated. In theseexamples, the document may be obtained from a third party that may beaccused of misappropriation or otherwise obtaining the trade secretwithout permission. Identification of the accused document may includeinput such as a naming indicator for the document and/or selection of adocument from a database of an electronic device displaying the userinterface, for example.

At block 904, the process 900 may include the electronic devicegenerating a document obfuscation value corresponding to the accuseddocument. For example, the document may be identified and the electronicdevice may cause a document obfuscation value to be generatedcorresponding to the document. For example, a obfuscation component mayreceive data corresponding to the document, such as from one or moredatabases and/or other storage locations associated with the electronicdevice and/or remote storage accessible by the electronic device. Theobfuscation component may then generate a document obfuscation valuecorresponding to the document. In general, the obfuscation component mayreceive, as input, text data, image data, formatting data, and/or otherdata corresponding to the document, and may generate, as output, adocument obfuscation value that corresponds to the input. In examples,the electronic device may include multiple obfuscation components thateach employ a different hashing algorithm. In these examples, eachobfuscation component may output a different document obfuscation valuefor the same document.

At block 906, the process 900 may include the registry system receivingthe document obfuscation value and request data indicating a request toidentify one or more trade secrets registered with the trade secretregistry that are similar to the accused document. For example, thedocument obfuscation value may be received from the electronic device,such as via a firewall. Additionally, the electronic device may havegenerated and sent request data indicating a request to identify one ormore trade secrets registered with the trade secret registry that aresimilar to the accused document.

At block 908, the process 900 may include the registry system analyzingthe document obfuscation value with respect to other documentobfuscation values associated with the one or more other trade secretsregistered with the trade secret registry. For example, a verificationcomponent may be configured to verify that a particular document hasbeen registered with the trade secret registry. For example, onceregistered, the verification component may be utilized to determine ifand/or verify that another document, such as a document accused to havebeen misappropriated, matches or is similar to the registered document.The verification component may be utilized to analyze the documentobfuscation value for the accused document with respect to otherdocument obfuscation values of registered documents.

At block 910, the process 900 may include the registry systemidentifying similar document obfuscation values. For example, if theverification component determines that at least one of the registereddocument obfuscation values matches the document obfuscation value forthe accused document, the verification component may determine that theaccused document is the same or similar to the registered document. Inother examples, the verification component may determine a degree ofsimilarity between the accused document and one or more registereddocuments.

Determining the degree of similarity may be performed as described abovewith respect to the comparison component 144 of FIG. 1. In theseexamples, the accused document may be determined to be similar to aregistered document when the degree of similarity meets or exceeds athreshold degree of similarity. In still other examples, theverification component may be configured to determine which portions ofan accused document match or are similar to at least one registereddocument. An indication of the matching or similar portions may bedisplayed, such as via the user interface(s). Additionally, in instanceswhere multiple versions of a document have been registered, theverification component may be configured to determine which of themultiple versions is most similar to the accused document, and mayprovide an indication of the version that is most similar.

At block 912, the process 900 may include the distributed-ledger systemverifying the similar document obfuscation value(s) are registered withthe blockchain. For example, the accused document obfuscation value maybe determined to match a registered document obfuscation value. In theseexamples, it may be advantageous to verify that the registered documentobfuscation value corresponds to a trade secret that has been registeredwith the blockchain. As such, the accused document obfuscation value maybe submitted to the distributed-ledger system, which may search theblockchain for the matching registered document obfuscation value and/orthe corresponding cryptographic document obfuscation value representingthe block in the blockchain where the trade secret is registered.

At block 914, the process 900 may include the registry system generatingverification data identifying the similar trade secret(s) and, inexamples, verifying registration with the blockchain. The registrysystem may receive, from the distributed-ledger system, data indicatingthat the accused document obfuscation value matches the registereddocument obfuscation value. In these and other examples, the registrysystem may generate verification data to be sent to the electronicdevice.

At block 916, the process 900 may include the electronic devicereceiving the verification data. For example, a verification status ofthe verification data may indicate that the accused document matches oris similar to at least one registered trade secret. A similarityindicator may indicate that the accused document is similar to, such apercentage similar to, at least one of the registered documents.Additionally, an identifier of the registered trade secret may beprovided. This may provide an indication to the user of the registeredtrade secret that is similar to the accused document.

At block 918, the process 900 may include the electronic deviceinitiating a claim-submission wizard to initiate the process of filingan insurance claim associated with the trade secret. In examples, a userinterface may display dialog boxes and/or input fields including textassociated with submitting a claim for insurance coverage in associationwith an insurance policy for the trade secret. In these examples, giventhat an allegation of trade secret misappropriation, or other legalclaim, may exist in light of the similarity between the accused documentand the registered trade secret, one or more wizards may be initiated toassist in filing a claim for insurance coverage. Input data may bereceived representing responses to the dialog boxes, and based at leastin part on receiving the input data, the input data may be formattedand/or sent to a remote system associated with an insurer indicatingthat a claim is to be filed and/or notifying the insurer of thepotential misappropriation and/or other legal action.

FIG. 10 illustrates a flow diagram of an example process for digitalproperty authentication. The order in which the operations or steps aredescribed is not intended to be construed as a limitation, and anynumber of the described operations may be combined in any order and/orin parallel to implement process 1000.

At block 1002, the process 1000 may include receiving, at an electronicdevice, data representing a document representing a trade secret. By wayof example, a user interface may include a selectable portion that, whenselected, may enable identification of a document representing a tradesecret. For example, the selectable portion and/or another portion ofthe user interface may include text requesting that a user of the userinterface select the selectable portion to identify a document to beregistered as a trade secret in association with the trade secretregistry. The user may provide input to the electronic device indicatingthe document to be registered as a trade secret. The input may includeselection of a naming indicator for the document.

At block 1004, the process 1000 may include receiving, at the electronicdevice, input indicating that the document is to be registered in atrade secret registry associated with a registry system, which may alsobe described herein as a first remote system. The input may be received,for example, via a user interface with one or more selectable portions.At least one of the selectable portions may be selected by the user toindicate that the document is to be registered with the trade secretregistry.

At block 1006, the process 1000 may include generating, based at leastin part on receiving the input, a document obfuscation valuerepresenting the document. For example, a obfuscation component mayreceive data corresponding to the document, such as from one or moredatabases and/or other storage locations associated with the electronicdevice and/or remote storage accessible by the electronic device. Theobfuscation component may then generate a document obfuscation valuecorresponding to the document. In general, the obfuscation component mayreceive, as input, text data, image data, formatting data, and/or otherdata corresponding to the document, and may generate, as output, adocument obfuscation value that corresponds to the input. In examples,the electronic device may include multiple obfuscation components thateach employ a different hashing algorithm. In these examples, eachobfuscation component may output a different document obfuscation valuefor the same document.

At block 1008, the process 1000 may include sending the documentobfuscation value and first request data indicating a first request togenerate a block in a blockchain associated with a distributed-ledgersystem, which may also be described herein as a second remote system.For example, a communications component of the electronic device mayformat and/or send the document obfuscation value to the registrysystem, and may generate the request data for sending to the registrysystem and/or the distributed-ledger system.

At block 1010, the process 1000 may include receiving, from the secondremote system, a cryptographic document obfuscation value representingthe block in the blockchain. For example, based at least in part onreceiving the document obfuscation value and/or the request data, acommunications component of the registry system and/or the electronicdevice may be configured to generate request data indicating a requestto register a trade secret in association with a blockchain, such as ablockchain associated with the distributed-ledger system. The requestdata may be sent to the distributed-ledger system along with, forexample, the document obfuscation value and/or an identifier of thedocument and/or the trade secret, and/or other information associatedwith the document and/or the trade secret.

The distributed-ledger system may receive the request data and thedocument obfuscation value (or other data) and may register the documentobfuscation value (or the other data) in association with a block of theblockchain. The distributed-ledger system may generate a cryptographicdocument obfuscation value representing the block in the blockchainand/or the distributed-ledger system may generate a time valueindicating a time and/or day that the document obfuscation value (or theother data) was registered with the blockchain. The distributed-ledgersystem may send the cryptographic document obfuscation value, the timevalue, and/or other information (such as a block number, for example) tothe registry system and/or the electronic device. The registry systemand/or the electronic device may receive the cryptographic documentobfuscation value from the distributed-ledger system.

At block 1012, the process 1000 may include sending, from the electronicdevice and to the first remote system, second request data representinga second request to register the document with respect to the tradesecret registry. This request data may be sent prior to or afterreceiving the cryptographic document obfuscation value.

At block 1014, the process 1000 may include generating, by the firstremote system, a record in the trade secret registry, the record:indicating that the trade secret has been registered in the trade secretregistry; including the cryptographic document obfuscation value; andindicating a time value associated with at least one of generation ofthe cryptographic document obfuscation value or generation of therecord. For example, a record generator of the registry system may thengenerate a record in the trade secret registry. For example, the recordmay include an identifier of the record, a naming indicator for thetrade secret, a description of the trade secret, a naming indicator ofthe document, one or more tags, a status identifier for the record, thedocument obfuscation value, the cryptographic document obfuscationvalue, the block number, the time value (also described as the blocktimestamp), insurance policy details, valuation details, and/or otherinformation associated with the trade secret. The record may be storedalong with one or more other records in the trade secret registry.

At block 1016, the process 1000 may include generating confirmation dataindicating that the record has been generated. The registry system, inexamples, may generate confirmation data indicating that the record hasbeen generated.

At block 1018, the process 1000 may include sending the confirmationdata from the first remote system to the electronic device. Receipt ofthe confirmation data may cause display of information, via the userinterface, indicating that the trade secret has been registered.

Additionally, or alternatively, the process 1000 may include identifyinga first portion and a second portion of the document and generating asecond document obfuscation value representing the first portion of thedocument and a third document obfuscation value representing the secondportion of the document. In these examples, generating the firstdocument obfuscation value may be based at least in part on the seconddocument obfuscation value and the third document obfuscation value. Forexample, the first document obfuscation value may be generated bygenerating a document obfuscation value of the second and third documentobfuscation values. Alternatively, the first document obfuscation valuemay be generated by combining the second and third document obfuscationvalues.

Additionally, or alternatively, the process 1000 may include sending, toan insurer system, the document obfuscation value and third request dataindicating a third request to generate a second block in a secondblockchain associated with the insurer system. The process 1000 may alsoinclude receiving, from the insurer system, a second cryptographicdocument obfuscation value representing the second block in the secondblockchain. In examples where the second cryptographic documentobfuscation value is received at the electronic device, the electronicdevice may send the second cryptographic document obfuscation value tothe registry system. In these and other examples, the record mayassociate the second cryptographic document obfuscation value with thetrade secret and may indicate a second time value associated withgeneration of the second cryptographic document obfuscation value.

Additionally, or alternatively, the process 1000 may include generatingtag data indicating properties associated with the document. Theproperties may include at least one of a title, a trade-secret type,and/or an identifier of at least one of a person or an entity associatedwith the document. The process 1000 may also include storing the tagdata in a database associated with the registry system. The tag data maybe associated with the document obfuscation value and/or the tradesecret. The process 1000 may also include receiving, at the registrysystem, input data requesting a search of trade secrets associated withthe trade secret registry. In these examples, the input data may includea search term. The process 1000 may also include causing, based at leastin part on receiving the input data, the tag data to be searched for thesearch term.

FIG. 11 illustrates a flow diagram of another example process fordigital property authentication. The order in which the operations orsteps are described is not intended to be construed as a limitation, andany number of the described operations may be combined in any orderand/or in parallel to implement process 1100.

At block 1102, the process 1100 may include receiving data representinga document representing a trade secret. By way of example, a userinterface may include a selectable portion that, when selected, mayenable identification of a document representing a trade secret. Forexample, the selectable portion and/or another portion of the userinterface may include text requesting that a user of the user interfaceselect the selectable portion to identify a document to be registered asa trade secret in association with the trade secret registry. The usermay provide input to the electronic device indicating the document to beregistered as a trade secret. The input may include selection of anaming indicator for the document.

At block 1104, the process 1100 may include receiving input indicatingthat the document is to be registered in a trade secret registryassociated with a registry system. The input may be received, forexample, via a user interface with one or more selectable portions. Atleast one of the selectable portions may be selected by the user toindicate that the document is to be registered with the trade secretregistry.

At block 1106, the process 1100 may include generating, based at leastin part on receiving the input, a document obfuscation valuerepresenting the document. For example, a obfuscation component mayreceive data corresponding to the document, such as from one or moredatabases and/or other storage locations associated with the electronicdevice and/or remote storage accessible by the electronic device. Theobfuscation component may then generate a document obfuscation valuecorresponding to the document. In general, the obfuscation component mayreceive, as input, text data, image data, formatting data, and/or otherdata corresponding to the document, and may generate, as output, adocument obfuscation value that corresponds to the input. In examples,the electronic device may include multiple obfuscation components thateach employ a different hashing algorithm. In these examples, eachobfuscation component may output a different document obfuscation valuefor the same document.

At block 1108, the process 1100 may include sending, to the registrysystem, the document obfuscation value and request data indicating arequest to register the trade secret in association with the tradesecret registry. For example, a communication component of theelectronic device may format and/or send the document obfuscation valueto the registry system. Additionally, the communication component maygenerate the request data for sending to the registry system.

At block 1110, the process 1100 may include receiving, from the registrysystem, confirmation data indicating that: the trade secret has beenregistered in association with the trade secret registry; and the tradesecret has been associated with a cryptographic document obfuscationvalue representing a block in a blockchain associated with adistributed-ledger system. For example, based at least in part onreceiving the document obfuscation value and/or the request data, acommunications component of the registry system and/or the electronicdevice may be configured to generate request data indicating a requestto register a trade secret in association with a blockchain, such as ablockchain associated with the distributed-ledger system. The requestdata may be sent to the distributed-ledger system along with, forexample, the document obfuscation value and/or an identifier of thedocument and/or the trade secret, and/or other information associatedwith the document and/or the trade secret.

The distributed-ledger system may receive the request data and thedocument obfuscation value (or other data) and may register the documentobfuscation value (or the other data) in association with a block of theblockchain. The distributed-ledger system may generate a cryptographicdocument obfuscation value representing the block in the blockchainand/or the distributed-ledger system may generate a time valueindicating a time and/or day that the document obfuscation value (or theother data) was registered with the blockchain. The distributed-ledgersystem may send the cryptographic document obfuscation value, the timevalue, and/or other information (such as a block number, for example) tothe registry system and/or the electronic device. The registry systemand/or the electronic device may receive the cryptographic documentobfuscation value from the distributed-ledger system.

The registry system may then generate the record in the trade secretregistry. For example, a record generator of the registry system maythen generate a record in the trade secret registry. For example, therecord may include an identifier of the record, a naming indicator forthe trade secret, a description of the trade secret, a naming indicatorof the document, one or more tags, a status identifier for the record,the document obfuscation value, the cryptographic document obfuscationvalue, the block number, the time value (also described as the blocktimestamp), insurance policy details, valuation details, and/or otherinformation associated with the trade secret. The record may be storedalong with one or more other records in the trade secret registry.

Additionally, or alternatively, the process 1100 may include identifyinga first portion and a second portion of the document and generating asecond document obfuscation value representing the first portion of thedocument and a third document obfuscation value representing the secondportion of the document. In these examples, generating the firstdocument obfuscation value may be based at least in part on the seconddocument obfuscation value and the third document obfuscation value. Forexample, the first document obfuscation value may be generated bygenerating a document obfuscation value of the second and third documentobfuscation values. Alternatively, the first document obfuscation valuemay be generated by combining the second and third document obfuscationvalues.

Additionally, or alternatively, the process 1100 may include receivingthe confirmation data indicating that the trade secret has beenassociated with a second cryptographic document obfuscation valuerepresenting a second block in a second blockchain associated with aninsurer system.

Additionally, or alternatively, the process 1100 may include generating,based at least in part on receiving the input, a second documentobfuscation value representing the document. In these examples, thesecond document obfuscation value may be generated utilizing a secondhash-value generator that differs from the first hash-value generator.The process 1100 may also include sending the second documentobfuscation value to the registry system. In these examples, theconfirmation data may indicate that the trade secret has been associatedwith a second cryptographic document obfuscation value associated withthe second document obfuscation value, and that the second cryptographicdocument obfuscation value represents a second block in a secondblockchain associated with a third system.

Additionally, or alternatively, the process 1100 may include receivingsecond input indicating at least one of a title associated with thedocument, a trade-secret type associated with the document, and/oridentifying information of at least one of a person or an entityassociated with the document. The process 1100 may also includegenerating tag data based at least in part on the second input andsending the tag data to the registry system. The process 1100 may alsoinclude receiving third input requesting a search of the trade secretregistry, where the third input includes a search term, and sending anindication of the third input to the registry system. The process 1100may also include receiving response data indicating a result of thesearch of at least the tag data as performed by the registry system.

Additionally, or alternatively, the process 1100 may include identifyingfields of the document, where individual ones of the fields may beassociated with a field type. The process 1100 may also includeidentifying a field value associated with the individual ones of thefields and generating tag data associated with the document based atleast in part on the field type and/or the field value for theindividual ones of the fields.

Additionally, or alternatively, the process 1100 may include storingsecurity rules associated with a firewall. In these examples, sendingthe document obfuscation value and the request data may be based atleast in part on the security rules allowing the transmission of thedocument obfuscation value and the request data to the registry system.Also, in these examples, receiving the confirmation data may be based atleast in part on the security rules allowing the receipt of theconfirmation data from the registry system.

FIG. 12 illustrates a flow diagram of another example process fordigital property authentication. The order in which the operations orsteps are described is not intended to be construed as a limitation, andany number of the described operations may be combined in any orderand/or in parallel to implement process 1200.

At block 1202, the process 1200 may include receiving, from anelectronic device, a document obfuscation value representing a documentcorresponding to a trade secret. For example, a obfuscation component ofthe electronic device may receive data corresponding to the document,such as from one or more databases and/or other storage locationsassociated with the electronic device and/or remote storage accessibleby the electronic device. The obfuscation component may then generate adocument obfuscation value corresponding to the document. In general,the obfuscation component may receive, as input, text data, image data,formatting data, and/or other data corresponding to the document, andmay generate, as output, a document obfuscation value that correspondsto the input. In examples, the electronic device may include multipleobfuscation components that each employ a different hashing algorithm.In these examples, each obfuscation component may output a differentdocument obfuscation value for the same document.

At block 1204, the process 1200 may include receiving input dataindicating that the trade secret is to be registered in a trade secretregistry. For example, a communication component of the electronicdevice may format and/or send the input data to the system.

At block 1206, the process 1200 may include sending, to a remote system,the document obfuscation value and request data indicating a request togenerate a block in a blockchain associated with the remote system. Forexample, a communications component of the electronic device may formatand/or send the document obfuscation value to the system, and maygenerate the request data for sending to the system and/or the remotesystem.

At block 1208, the process 1200 may include receiving, from the remotesystem, a cryptographic document obfuscation value representing theblock in the blockchain. For example, based at least in part onreceiving the document obfuscation value and/or the request data, acommunications component of the system and/or the electronic device maybe configured to generate request data indicating a request to registera trade secret in association with a blockchain, such as a blockchainassociated with the remote system. The request data may be sent to theremote system along with, for example, the document obfuscation valueand/or an identifier of the document and/or the trade secret, and/orother information associated with the document and/or the trade secret.

The remote system may receive the request data and the documentobfuscation value (or other data) and may register the documentobfuscation value (or the other data) in association with a block of theblockchain. The remote system may generate a cryptographic documentobfuscation value representing the block in the blockchain and/or theremote system may generate a time value indicating a time and/or daythat the document obfuscation value (or the other data) was registeredwith the blockchain. The remote system may send the cryptographicdocument obfuscation value, the time value, and/or other information(such as a block number, for example) to the system and/or theelectronic device. The system and/or the electronic device may receivethe cryptographic document obfuscation value from the remote system.

At block 1210, the process 1200 may include generating a record in thetrade secret registry, the record: indicating that the trade secret hasbeen registered in the trade secret registry; and including thecryptographic document obfuscation value. For example, a recordgenerator of the system may then generate a record in the trade secretregistry. For example, the record may include an identifier of therecord, a naming indicator for the trade secret, a description of thetrade secret, a naming indicator of the document, one or more tags, astatus identifier for the record, the document obfuscation value, thecryptographic document obfuscation value, the block number, the timevalue (also described as the block timestamp), insurance policy details,valuation details, and/or other information associated with the tradesecret. The record may be stored along with one or more other records inthe trade secret registry.

Additionally, or alternatively, the process 1200 may include receiving,from the electronic device, a second document obfuscation valuerepresenting the document and second, to a distributed-ledger system,the second document obfuscation value and second request data indicatinga second request to generate a second block in a second blockchainassociated with the distributed-ledger system. The process 1200 may alsoinclude receiving, from the distributed-ledger system, a secondcryptographic document obfuscation value representing the second blockin the second blockchain. In these examples, the record may associatethe second cryptographic document obfuscation value with the tradesecret.

Additionally, or alternatively, the process 1200 may include receivingan identifier corresponding to at least one of the electronic deviceand/or an entity associated with the electronic device. The process 1200may also include associating the identifier with the first record anddetermining that a second record associated with the trade secretregistry is associated with the identifier. The process 1200 may alsoinclude associating the first record with the second record based atleast in part on determining that the first record and the second recordare associated with the identifier.

Additionally, or alternatively, the process 1200 may include sending, toa distributed-ledger system, the document obfuscation value and secondrequest data indicating a second request to generate a second block in asecond blockchain associated with the distributed-ledger system. Theprocess 1200 may also include receiving, from the distributed-ledgersystem, a second cryptographic document obfuscation value representingthe second block in the second blockchain. In these examples, the recordmay associate the second cryptographic document obfuscation value withthe trade secret.

Additionally, or alternatively, the process 1200 may include receivingsecond input data indicating at least one of a title associated with thedocument, a trade-secret type associated with the document, or anidentifier of at least one of a person or an entity associated with thedocument. The process 1200 may also include generating tag data based atleast in part on the second input data. The process 1200 may alsoinclude receiving third input data requesting a search of trade secretsassociated with the trade secret registry, where the third input datamay include a search term. The process 1200 may also include causing,based at least in part on receiving the third input data, the tag datato be searched for the search term.

Additionally, or alternatively, the process 1200 may include identifyingfields of the document, where individual ones of the fields may beassociated with a field type. The process 1200 may also includeidentifying a field value associated with the individual ones of thefields and generating tag data associated with the document based atleast in part on the field type and/or the field value for theindividual ones of the fields.

FIG. 13 illustrates a flow diagram of another example process fordigital property authentication. The order in which the operations orsteps are described is not intended to be construed as a limitation, andany number of the described operations may be combined in any orderand/or in parallel to implement process 1300.

At block 1302, the process 1300 may include receiving, from anelectronic device, data representing a document corresponding to a tradesecret. By way of example, a user interface may include a selectableportion that, when selected, may enable identification of a documentrepresenting a trade secret. For example, the selectable portion and/oranother portion of the user interface may include text requesting that auser of the user interface select the selectable portion to identify adocument to be registered as a trade secret in association with thetrade secret registry. The user may provide input to the electronicdevice indicating the document to be registered as a trade secret. Theinput may include selection of a naming indicator for the document.

At block 1304, the process 1300 may include receiving input dataindicating that the document is to be registered in a trade secretregistry. The input may be received, for example, via a user interfacewith one or more selectable portions. At least one of the selectableportions may be selected by the user to indicate that the document is tobe registered with the trade secret registry.

At block 1306, the process 1300 may include generating, based at leastin part on receiving the input data, a document obfuscation valuerepresenting the document. For example, a obfuscation component of theelectronic device and/or the system associated with the trade secretregistry may receive data corresponding to the document, such as fromone or more databases and/or other storage locations associated with theelectronic device and/or the system, and/or remote storage accessible bythe electronic device and/or the system. The obfuscation component maythen generate a document obfuscation value corresponding to thedocument. In general, the obfuscation component may receive, as input,text data, image data, formatting data, and/or other data correspondingto the document, and may generate, as output, a document obfuscationvalue that corresponds to the input. In examples, the electronic devicemay include multiple obfuscation components that each employ a differenthashing algorithm. In these examples, each obfuscation component mayoutput a different document obfuscation value for the same document.

At block 1308, the process 1300 may include removing the document fromthe system. For example, once the document obfuscation value isgenerated, for security reasons among others, the document may beremoved from the system such that it is not stored or otherwiseavailable to anyone accessing the system, other than the electronicdevice from which the document was received.

At block 1310, the process 1300 may include sending, to a remote system,the document obfuscation value and request data indicating a request togenerate a block in a blockchain associated with the remote system. Forexample, a communication component of the system may format and/or sendthe document obfuscation value and the request data to the remotesystem.

At block 1312, the process 1300 may include receiving, from the remotesystem, a cryptographic document obfuscation value representing theblock in the blockchain. For example, based at least in part onreceiving the document obfuscation value and/or the request data, acommunications component of the system and/or the electronic device maybe configured to generate request data indicating a request to registera trade secret in association with a blockchain, such as a blockchainassociated with the remote system. The request data may be sent to theremote system along with, for example, the document obfuscation valueand/or an identifier of the document and/or the trade secret, and/orother information associated with the document and/or the trade secret.

The remote system may receive the request data and the documentobfuscation value (or other data) and may register the documentobfuscation value (or the other data) in association with a block of theblockchain. The remote system may generate a cryptographic documentobfuscation value representing the block in the blockchain and/or theremote system may generate a time value indicating a time and/or daythat the document obfuscation value (or the other data) was registeredwith the blockchain. The remote system may send the cryptographicdocument obfuscation value, the time value, and/or other information(such as a block number, for example) to the system and/or theelectronic device. The system and/or the electronic device may receivethe cryptographic document obfuscation value from the remote system.

At block 1314, the process 1300 may include generating a record in thetrade secret registry, the record: indicating that the trade secret hasbeen registered in the trade secret registry; including thecryptographic document obfuscation value; and indicating a time valueassociated with at least one of generation of the cryptographic documentobfuscation value or generation of the record. For example, a recordgenerator of the system may then generate a record in the trade secretregistry. For example, the record may include an identifier of therecord, a naming indicator for the trade secret, a description of thetrade secret, a naming indicator of the document, one or more tags, astatus identifier for the record, the document obfuscation value, thecryptographic document obfuscation value, the block number, the timevalue (also described as the block timestamp), insurance policy details,valuation details, and/or other information associated with the tradesecret. The record may be stored along with one or more other records inthe trade secret registry.

Additionally, or alternatively, the process 1300 may include generating,based at least in part on receiving the input data, a second documentobfuscation value representing the document, the second documentobfuscation value generated utilizing a second hash-value generator thatdiffers from the first hash-value generator. The process 1300 may alsoinclude sending, to a distributed-ledger system, the second documentobfuscation value and second request data indicating a second request togenerate a second block in a second blockchain associated with thedistributed-ledger system. The process 1300 may also include receiving,from the distributed-ledger system, a second cryptographic documentobfuscation value representing the second block in the secondblockchain. In these examples, the record may associate the secondcryptographic document obfuscation value with the trade secret.

Additionally, or alternatively, the process 1300 may include receivingan identifier corresponding to at least one of the electronic deviceand/or an entity associated with the electronic device. The process 1300may also include associating the identifier with the first record anddetermining that a second record associated with the trade secretregistry is associated with the identifier. The process 1300 may alsoinclude associating the first record with the second record based atleast in part on determining that the first record and the second recordare associated with the identifier.

Additionally, or alternatively, the process 1300 may include identifyinga first portion and a second portion of the document and generating asecond document obfuscation value representing the first portion of thedocument and a third document obfuscation value representing the secondportion of the document. In these examples, generating the firstdocument obfuscation value may be based at least in part on the seconddocument obfuscation value and the third document obfuscation value. Forexample, the first document obfuscation value may be generated bygenerating a document obfuscation value of the second and third documentobfuscation values. Alternatively, the first document obfuscation valuemay be generated by combining the second and third document obfuscationvalues.

Additionally, or alternatively, the process 1300 may include sending, toa distributed-ledger system, the document obfuscation value and secondrequest data indicating a second request to generate a second block in asecond blockchain associated with the distributed-ledger system. Theprocess 1300 may also include receiving, from the distributed-ledgersystem, a second cryptographic document obfuscation value representingthe second block in the second blockchain. In these examples, the recordmay associate the second cryptographic document obfuscation value withthe trade secret.

Additionally, or alternatively, the process 1300 may include receivingsecond input data indicating at least one of a title associated with thedocument, a trade-secret type associated with the document, or anidentifier of at least one of a person or an entity associated with thedocument. The process 1300 may also include generating tag data based atleast in part on the second input data. The process 1300 may alsoinclude receiving third input data requesting a search of trade secretsassociated with the trade secret registry, where the third input datamay include a search term. The process 1300 may also include causing,based at least in part on receiving the third input data, the tag datato be searched for the search term.

Additionally, or alternatively, the process 1300 may include identifyingfields of the document, where individual ones of the fields may beassociated with a field type. The process 1300 may also includeidentifying a field value associated with the individual ones of thefields and generating tag data associated with the document based atleast in part on the field type and/or the field value for theindividual ones of the fields.

Additionally, or alternatively, the process 1300 may include storingsecurity rules associated with a firewall. In these examples, receivingthe data representing the document may be based at least in part on thesecurity rules allowing the receipt of the data from the electronicdevice. Additionally, sending the document obfuscation value and therequest data may be based at least in part on the security rulesallowing the transmission of the document obfuscation value and therequest data to the remote system. Additionally, sending theconfirmation data may be based at least in part on the security rulesallowing the transmission of the confirmation data to the electronicdevice.

FIG. 14 illustrates a flow diagram of an example process for identifyingdistinctions between documents associated with a digital propertyauthentication and management system. The order in which the operationsor steps are described is not intended to be construed as a limitation,and any number of the described operations may be combined in any orderand/or in parallel to implement process 1400.

At block 1402, the process 1400 may include receiving, from anelectronic device, a document obfuscation value representing a documentcorresponding to a trade secret. For example, a obfuscation component ofthe electronic device may receive data corresponding to the document,such as from one or more databases and/or other storage locationsassociated with the electronic device and/or remote storage accessibleby the electronic device. The obfuscation component may then generate adocument obfuscation value corresponding to the document. In general,the obfuscation component may receive, as input, text data, image data,formatting data, and/or other data corresponding to the document, andmay generate, as output, a document obfuscation value that correspondsto the input. In examples, the electronic device may include multipleobfuscation components that each employ a different hashing algorithm.In these examples, each obfuscation component may output a differentdocument obfuscation value for the same document.

At block 1404, the process 1400 may include receiving first request dataindicating a request to register the trade secret in association with atrade secret registry. For example, a communication component of theelectronic device may format and/or send the input data to the system.

At block 1406, the process 1400 may include analyzing the documentobfuscation value in relation to stored document obfuscation valuesstored in association with the trade secret registry. For example, acomparison component may be configured to analyze the documentobfuscation values and determine degrees of similarity and/or degrees ordifferences between the document obfuscation values and/or the documentscorresponding to the document obfuscation values. For example, asdescribed above, the obfuscation component(s) may generate documentobfuscation values corresponding to documents representing tradesecrets. Similar documents may have similar document obfuscation values.As such, the comparison component may analyze the document obfuscationvalues to determine a degree of similarity between them. A thresholddegree of similarity may be identified and/or determined and the degreeof similarity between document obfuscation values may be compared to thethreshold degree of similarity. Document obfuscation values with adegree of similarity that meets or exceeds the threshold degree ofsimilarity may be determined to be similar, while hash-value pairs thatfall below the threshold degree of similarity may be determined to bedissimilar. Additionally, document obfuscation values may be segmentedand the segments may be compared to determine portions of the documentobfuscation values that are similar and portions that are not. Thenumber of similar versus dissimilar document obfuscation values may beutilized to determine an overall degree of similarity between documentobfuscation values.

In other examples, a feature vector may be associated with some or allof the document obfuscation values. The feature vector may correspond tocharacteristics of the document obfuscation value and/or the document.For example, the presence or absence of text data and/or image data fromthe document may impact the feature vector. In other examples, the textdata and/or image data itself may impact the feature vector. Otherfactors such as document length, the entity associated with thedocument, creation date, modification date, and/or other metadata mayimpact the feature vector. By way of example, a feature may be describedas an individual measurable property or characteristic of a document. Agiven feature may be numeric and/or may be considered a string and/or agraphic. A set of such features may be described as a feature vector. Assuch, similar feature vectors indicate similar characteristics and/orproperties of the documents they represent. A similarity and/orpopularity score may be determined for a given pair of feature vectors,with more favorable scores indicating a high degree of similaritybetween documents.

In other examples, Levenshtein distances may be utilized to determine adegree of similarity between trade secrets. A Levenshtein distance maybe determined between two document obfuscation values and/or documents.A shorter Levenshtein distance may indicate more similarity than alonger Levenshtein distance. As used herein, a Levenshtein distance,also known as an edit distance, may be described as a string metric formeasuring the difference between two sequences. For example, theLevenshtein distance between two words may be considered the minimumnumber of single-character edits to change one word into the other. Assuch, the Levenshtein distance between two very similar words would beshorter than a Levenshtein distance between two very different words. Inthese examples, a Levenshtein distance may be determined between twodocuments and/or two document obfuscation values representing thosedocuments, with shorter Levenshtein distances indicating more similaritybetween documents.

The comparison component may be configured to determine if ato-be-registered trade secret is unique with respect to other tradesecrets registered in association with the trade secret registry. Forexample, the document obfuscation values and/or documents may beanalyzed as described herein to determine whether a given documentobfuscation value is different from one or more stored documentobfuscation values associated with registered trade secrets. If thedocument obfuscation value is different, then the to-be-registered tradesecret may be identified as or determined to be unique with respect toother trade secrets associated with the trade secret registry. Inexamples, determining that the document obfuscation value is differentfrom the stored document obfuscation values may include determining adegree of similarity between the document obfuscation values anddetermining that the degree of similarity does not exceed a thresholddegree of similarity.

At block 1408, the process 1400 may include determining, based at leastin part on analyzing the document obfuscation value in relation to thestored document obfuscation values, that the document obfuscation valueis different from the stored document obfuscation values. For example,determining that the document obfuscation value is different from thestored document obfuscation values may be based at least in part on theresults from the comparison component as described with respect to block1406.

At block 1410, the process 1400 may include receiving, from the remotesystem, a cryptographic document obfuscation value associated with thedocument obfuscation value, the cryptographic document obfuscation valuerepresenting a block in the blockchain. For example, based at least inpart on receiving the document obfuscation value and/or the requestdata, a communications component of the system and/or the electronicdevice may be configured to generate request data indicating a requestto register a trade secret in association with a blockchain, such as ablockchain associated with the remote system. The request data may besent to the remote system along with, for example, the documentobfuscation value and/or an identifier of the document and/or the tradesecret, and/or other information associated with the document and/or thetrade secret.

At block 1412, the process 1400 may include generating, based at leastin part on determining that the document obfuscation value is differentfrom the stored document obfuscation values, a record in the tradesecret registry, the record: indicating that the trade secret has beenregistered in the trade secret registry; and associating thecryptographic document obfuscation value with the trade secret. Forexample, a record generator of the system may then generate a record inthe trade secret registry. For example, the record may include anidentifier of the record, a naming indicator for the trade secret, adescription of the trade secret, a naming indicator of the document, oneor more tags, a status identifier for the record, the documentobfuscation value, the cryptographic document obfuscation value, theblock number, the time value (also described as the block timestamp),insurance policy details, valuation details, and/or other informationassociated with the trade secret. The record may be stored along withone or more other records in the trade secret registry.

Additionally, or alternatively, the process 1400 may include associatingthe trade secret with at least one trade secret associated with the atleast one of the stored document obfuscation values based at least inpart on determining that a degree of similarity between the documentobfuscation value and a stored document obfuscation value is greaterthan a threshold degree of similarity and/or determining that an entityidentifier associated with the document obfuscation value is associatedwith the store document obfuscation value.

Additionally, or alternatively, the process 1400 may include generatingconfirmation data indicating that the record has been associated withthe trade secret registry and/or the document has been determined to beunique with respect to other documents registered in association withthe trade secret registry. The process 1400 may also include sending theconfirmation data to the electronic device, such as for display via auser interface.

FIG. 15 illustrates a flow diagram of an example process associated witha user interface in accordance with a digital property authenticationand management system. The order in which the operations or steps aredescribed is not intended to be construed as a limitation, and anynumber of the described operations may be combined in any order and/orin parallel to implement process 1500.

At block 1502, the process 1500 may include causing display of a userinterface including a first selectable portion indicating an option toregister a trade secret in a trade secret registry associated with aremote system. For example, the user interface may be cause to bedisplayed on a screen of an electronic device. The first selectableportion may be displayed via the user interface in a manner such that auser may provide input to select the selectable portion. In examples,the first selectable portion may include text such as “register,” whichmay provide an indication of the functionality associated with selectionof the first selectable portion.

At block 1504, the process 1500 may include receiving, via the userinterface, first input indicating selection of the first selectableportion. The input may be received via touch input on the screen of theelectronic device and/or by tactile and/or audible input using, forexample, an instrument such as a mouse or keyboard.

At block 1506, the process 1500 may include causing, based at least inpart on receiving the first input, display of a second selectableportion requesting identification of a document to be registered as thetrade secret. Causing display of the second selectable portion may bethe same or similar to causing display of the first selectable portion,as described with respect to block 1502.

At block 1508, the process 1500 may include receiving, utilizing thesecond selectable portion of the user interface, second inputidentifying the document. Identification of the document may includeinput such as a naming indicator for the document and/or selection of adocument from a database of an electronic device displaying the userinterface, for example. The document may be identified and theelectronic device may cause a document obfuscation value to be generatedcorresponding to the document. For example, a obfuscation component mayreceive data corresponding to the document, such as from one or moredatabases and/or other storage locations associated with the electronicdevice and/or remote storage accessible by the electronic device. Theobfuscation component may then generate a document obfuscation valuecorresponding to the document. In general, the obfuscation component mayreceive, as input, text data, image data, formatting data, and/or otherdata corresponding to the document, and may generate, as output, adocument obfuscation value that corresponds to the input. In examples,the electronic device may include multiple obfuscation components thateach employ a different hashing algorithm. In these examples, eachobfuscation component may output a different document obfuscation valuefor the same document.

At block 1510, the process 1500 may include causing, based at least inpart on the second input, display of a record associated with the tradesecret registry, the record indicating: that a document obfuscationvalue generated based at least in part on the document has beenregistered in association with the trade secret registry; that acryptographic document obfuscation value associated with a block of ablockchain has been registered in association with the trade secretregistry; and a time value associated with at least one of generation ofthe cryptographic document obfuscation value or generation of therecord. The record may include a record identifier, trade-secretdetails, and/or transaction details. The record identifier may includenumbers and/or letters that identify the record with respect to thetrade secret registry. The trade-secret details may, for example,include a naming indicator for the trade secret, a description of thetrade secret, a naming indicator for the document representing the tradesecret, and/or the tags generated as described elsewhere herein. Thetransaction details may include a status of the registration with thetrade secret registry, the document obfuscation value, a block numberassociated with the block at which the trade secret is registered withthe blockchain, the cryptographic document obfuscation value (alsodescribed as the block document obfuscation value), and/or the blocktimestamp. Other information that may be included in the record anddisplayed with respect to the user interface may include insurancepolicy details, valuation details, and/or other information associatedwith the trade secret, as described more fully elsewhere herein.

The record may be generated by a record generator of the remote systemassociated with the trade secret registry. The record may be storedalong with one or more other records in the trade secret registry. Theremote system, in examples, may generate confirmation data indicatingthat the record has been generated, and the confirmation data may besent to the electronic device for display via a user interface.

Additionally, or alternatively, the process 1500 may include causingdisplay of a third selectable portion indicating a second option toacquire an insurance policy associated with the trade secret andreceiving, via the user interface, third input indicating selection ofthe third selectable portion. The process 1500 may also include causing,based at least in part on receiving the third input, display of one ormore requests for information associated with at least one of theinsurance policy or the trade secret. Also, one or more input fieldsconfigured to receive textual input in response to the one or morerequests for information may be caused to be displayed. The process 1500may also include receiving, via the user interface, the textual input toindividual ones of the one or more input fields and receiving, from adistributed-ledger system associated with an insurer, an indication thatthe insurance policy has been issued. The process 1500 may also includecausing display, via the user interface, of insurance-policy informationassociated with the insurance policy.

Additionally, or alternatively, the process 1500 may include causingdisplay, via the user interface, of input fields associated with thedocument. In these examples, the input fields may include at least oneof a document-name field, a document-description field, and/or a tagfield. The process 1500 may also include causing display, via the userinterface, of a third selectable portion indicating a second option toauto-populate at least one of the input fields. The process 1500 mayalso include receiving, via the user interface, third input indicatingselection of the third selectable portion and causing, based at least inpart on the third input, display of text in the at least one of theinput fields.

Additionally, or alternatively, the process 1500 may include causingdisplay, via the user interface, of a third selectable option indicatinga second option to associate an information document with the tradesecret. In these examples, the informational document may indicateinformation associated with a value of the trade secret. The process1500 may also include receiving, utilizing the third selectable portionof the user interface, third input identifying the information document.The process 1500 may also include causing display, via the userinterface, of the value determined by the remote system based at leastin part on the information document. In these examples, the record mayindicate a second cryptographic document obfuscation value associatedwith a second block of the blockchain where the information document hasbeen registered.

FIG. 16 illustrates a flow diagram of another example process associatedwith a user interface in accordance with a digital propertyauthentication and management system. The order in which the operationsor steps are described is not intended to be construed as a limitation,and any number of the described operations may be combined in any orderand/or in parallel to implement process 1600.

At block 1602, the process 1600 may include causing display of a userinterface including a first selectable portion indicating an option toregister a trade secret in a trade secret registry. For example, theuser interface may be cause to be displayed on a screen of an electronicdevice. The first selectable portion may be displayed via the userinterface in a manner such that a user may provide input to select theselectable portion. In examples, the first selectable portion mayinclude text such as “register,” which may provide an indication of thefunctionality associated with selection of the first selectable portion.

At block 1604, the process 1600 may include receiving first input dataindicating selection of the first selectable portion. The input may bereceived via touch input on the screen of the electronic device and/orby tactile and/or audible input using, for example, an instrument suchas a mouse or keyboard.

At block 1606, the process 1600 may include causing display of a secondselectable portion requesting identification of a document to beregistered as the trade secret. Causing display of the second selectableportion may be the same or similar to causing display of the firstselectable portion, as described with respect to block 1602.

At block 1608, the process 1600 may include receiving second input dataidentifying the document. Identification of the document may includeinput such as a naming indicator for the document and/or selection of adocument from a database of an electronic device displaying the userinterface, for example. The document may be identified and theelectronic device may cause a document obfuscation value to be generatedcorresponding to the document. For example, a obfuscation component mayreceive data corresponding to the document, such as from one or moredatabases and/or other storage locations associated with the electronicdevice and/or remote storage accessible by the electronic device. Theobfuscation component may then generate a document obfuscation valuecorresponding to the document. In general, the obfuscation component mayreceive, as input, text data, image data, formatting data, and/or otherdata corresponding to the document, and may generate, as output, adocument obfuscation value that corresponds to the input. In examples,the electronic device may include multiple obfuscation components thateach employ a different hashing algorithm. In these examples, eachobfuscation component may output a different document obfuscation valuefor the same document.

At block 1610, the process 1600 may include causing display of acryptographic document obfuscation value associated with a block of ablockchain at which an identifier of the document has been registered.The cryptographic document obfuscation value may be a portion of arecord, which may also include a record identifier, trade-secretdetails, and/or transaction details. The record identifier may includenumbers and/or letters that identify the record with respect to thetrade secret registry. The trade-secret details may, for example,include a naming indicator for the trade secret, a description of thetrade secret, a naming indicator for the document representing the tradesecret, and/or the tags generated as described elsewhere herein. Thetransaction details may include a status of the registration with thetrade secret registry, the document obfuscation value, a block numberassociated with the block at which the trade secret is registered withthe blockchain, the cryptographic document obfuscation value (alsodescribed as the block document obfuscation value), and/or the blocktimestamp. Other information that may be included in the record anddisplayed with respect to the user interface may include insurancepolicy details, valuation details, and/or other information associatedwith the trade secret, as described more fully elsewhere herein.

Additionally, or alternatively, the process 1600 may include causingdisplay of a third selectable portion indicating a second option toacquire an insurance policy associated with the trade secret andreceiving, via the user interface, third input indicating selection ofthe third selectable portion. The process 1600 may also include causing,based at least in part on receiving the third input, display of one ormore requests for information associated with at least one of theinsurance policy or the trade secret. Also, one or more input fieldsconfigured to receive textual input in response to the one or morerequests for information may be caused to be displayed. The process 1600may also include receiving, via the user interface, the textual input toindividual ones of the one or more input fields and receiving, from adistributed-ledger system associated with an insurer, an indication thatthe insurance policy has been issued. The process 1600 may also includecausing display, via the user interface, of insurance-policy informationassociated with the insurance policy.

Additionally, or alternatively, the process 1600 may include causingdisplay, via the user interface, of input fields associated with thedocument. In these examples, the input fields may include at least oneof a document-name field, a document-description field, and/or a tagfield. The process 1600 may also include causing display, via the userinterface, of a third selectable portion indicating a second option toauto-populate at least one of the input fields. The process 1600 mayalso include receiving, via the user interface, third input indicatingselection of the third selectable portion and causing, based at least inpart on the third input, display of text in the at least one of theinput fields.

Additionally, or alternatively, the process 1600 may include receivinginput data representing user input to manipulate text from the inputfields. The process 1600 may also include causing display, with respectto the input field, of manipulated text based at least in part on thefourth input data. The process 1600 may also include causing display,via the user interface, of a fourth selectable portion requestingconfirmation of the manipulated text as displayed in the input field.The process 1600 may also include receiving, via the user interface,input data indicating selection of the selectable portion and causing,based at least in part on the input data, the manipulated text to beassociated with the identifier of the document.

Additionally, or alternatively, the process 1600 may include causingdisplay, via the user interface, of a third selectable option indicatinga second option to associate an information document with the tradesecret. In these examples, the informational document may indicateinformation associated with a value of the trade secret. The process1600 may also include receiving, utilizing the third selectable portionof the user interface, third input identifying the information document.The process 1600 may also include causing display, via the userinterface, of the value determined by the remote system based at leastin part on the information document. In these examples, the record mayindicate a second cryptographic document obfuscation value associatedwith a second block of the blockchain where the information document hasbeen registered.

Additionally, or alternatively, the process 1600 may include determininga characteristic of the document based at least in part on a documentobfuscation value corresponding to the document and determining, basedat least in part on the characteristic, a trade-secret type associatedwith the document. The process 1600 may also include causing display,via the user interface, of text indicating the trade-secret type.

Additionally, or alternatively, the process 1600 may include causingdisplay, via the user interface, of a trade-secret repository screenincluding the first identifier of the first document associated with anentity identifier, a second identifier of a second document associatedwith the entity identifier, and/or a search field configured to receiveinput to search records in the trade secret registry associated with theentity identifier. The process 1600 may also include receiving thirdinput data indicating text as entered into the search field and causingdisplay, via the user interface, of one or more of the records based atleast in part on the text as entered into the search field.

Additionally, or alternatively, the process 1600 may include causingdisplay, via the user interface, of a third selectable portionindicating a second option to verify that a second document correspondsto the first document. The process 1600 may also include receiving thirdinput data indicating selection of the third selection portion andcausing display of a fourth selectable portion requesting identificationof the second document. The process 1600 may also include receivingfourth input data identifying the second document and causing display,via the user interface, of an indication that a first documentobfuscation value associated with the first document has at least athreshold degree of similarity with a second document obfuscation valueassociated with the second document.

Additionally, or alternatively, the process 1600 may include determiningthat a first document obfuscation value associated with a first documenthas at least a threshold degree of similarity with a second documentobfuscation value associated with the second document, and associatingthe first document with the second document based at least in part ondetermining that the first document obfuscation value has at least athreshold degree of similarity with the second document obfuscationvalue. The process 1600 may also include causing display, via the userinterface, of an indication that the first document has been associatedwith the second document.

Additionally, or alternatively, the process 1600 may include determiningthat a first document obfuscation value associated with the document hasless than a threshold degree of similarity with document obfuscationvalues registered in association with the trade secret registry anddetermining, based at least in part on the first document obfuscationvalue having less than the threshold degree of similarity with thedocument obfuscation values, that the document is unique with respect tothe trade secret registry. The process 1600 may also include causingdisplay, via the user interface, of an indication that the document isunique with respect to the trade secret registry.

Additionally, or alternatively, the process 1600 may include causingdisplay, via the user interface, of insurance-policy informationassociated with an insurance policy issued for the trade secret. Inthese examples, the insurance-policy information may include a payoutvalue associated with an amount of money to be paid to an entityassociated with the trade secret upon the occurrence of an event. Theprocess 1600 may also include receiving compliance data indicating thatthe entity has not complied with a condition of the insurance policy andcausing display, via the user interface, of updated insurance-policyinformation including an updated payout value, the updated payout valuebeing less than the payout value.

Additionally, or alternatively, the process 1600 may include causingdisplay, via the user interface, of a second selectable portionindicating an option to verify that a second document is similar to thefirst document. The process 1600 may also include receiving second inputdata indicating selection of the second selectable portion and causingdisplay of a third selectable portion requesting identification of thesecond document. The process 1600 may also include receiving third inputdata identifying the second document and causing display, via the userinterface, of an indication that a first document obfuscation valueassociated with the first document has at least a threshold degree ofsimilarity with a second document obfuscation value associated with thesecond document.

FIG. 17 illustrates a flow diagram of an example process for digitalproperty management including document versioning. The order in whichthe operations or steps are described is not intended to be construed asa limitation, and any number of the described operations may be combinedin any order and/or in parallel to implement process 1700.

At block 1702, the process 1700 may include storing, in association witha trade secret registry, a first record indicating: a first documentobfuscation value corresponding to a first document representing a tradesecret; and a cryptographic document obfuscation value generated basedat least in part on the first document obfuscation value, thecryptographic document obfuscation value representing a block in ablockchain of a remote system. For example, a system associated with thetrade secret registry may store records corresponding to trade secretsregistered with the trade secret registry. Those records may includeinformation such as document obfuscation values generated based at leastin part on documents representing the trade secrets. The documentobfuscation values may be generated by an electronic device of a userand/or by the system associated with the trade secret registry.Additionally, the electronic device and/or the system may request thatthe trade secret and/or the document obfuscation value be registered inassociation with a blockchain of a remote system. The remote system mayregister such trade secrets and may generate cryptographic documentobfuscation values representing blocks of the blockchain.

At block 1704, the process 1700 may include receiving an indication thatthe first document represents a first version of the first document. Forexample, the indication may be received from the electronic device. Inother examples, the system may determine that the first documentrepresents the first version.

At block 1706, the process 1700 may include receiving, from anelectronic device, input data requesting to register a second documentin association with the trade secret registry. For example, acommunication component of the electronic device may send dataindicating a request to register the second document in association withthe trade secret registry.

At block 1708, the process 1700 may include receiving, from theelectronic device, a second document obfuscation value corresponding tothe second document. For example, the communication component may alsosend the document obfuscation value generated based at least in part onthe second document. A obfuscation component may receive datacorresponding to the document, such as from one or more databases and/orother storage locations associated with the electronic device and/orremote storage accessible by the electronic device. The obfuscationcomponent may then generate a document obfuscation value correspondingto the document. In general, the obfuscation component may receive, asinput, text data, image data, formatting data, and/or other datacorresponding to the document, and may generate, as output, a documentobfuscation value that corresponds to the input. In examples, theelectronic device may include multiple obfuscation components that eachemploy a different hashing algorithm. In these examples, eachobfuscation component may output a different document obfuscation valuefor the same document.

At block 1710, the process 1700 may include determining, based at leastin part on a comparison of the first document obfuscation value with thesecond document obfuscation value, that the second document correspondsto a second version of the first document. For example, a versioningcomponent may be configured to determine that two or more documentsand/or trade secrets are versions of the same document and/or tradesecret. For example, the results from a comparison component, asdescribed more fully above with respect to FIG. 1, may be utilized todetermine that two documents are similar in one or more respects but notthe same. The versioning component may further receive, identify,determine, and/or generate information indicating that the two documentsare associated with the same and/or a related entity identifier. Theversioning component may further receive, identify, determine, and/orgenerate information indicating that the two documents are associatedwith the same or a similar trade-secret type. Utilizing some or all ofthis information, the versioning component may determine that the twodocuments are versions of the same document. An indication of thisversioning may be stored with respect to the record(s) associated withthe documents and/or a visual indication may be displayed via a userinterface.

At block 1712, the process 1700 may include generating a second record:indicating that an identifier of the second document has been registeredin association with the trade secret registry; indicating that thesecond document is the second version of the first document; andincluding a selectable link that, when selected, causes display of thefirst record. The record may include a record identifier, trade-secretdetails, and/or transaction details. The record identifier may includenumbers and/or letters that identify the record with respect to thetrade secret registry. The trade-secret details may, for example,include a naming indicator for the trade secret, a description of thetrade secret, a naming indicator for the document representing the tradesecret, and/or the tags generated as described elsewhere herein. Thetransaction details may include a status of the registration with thetrade secret registry, the document obfuscation value, a block numberassociated with the block at which the trade secret is registered withthe blockchain, the cryptographic document obfuscation value (alsodescribed as the block document obfuscation value), and/or the blocktimestamp. Other information that may be included in the record anddisplayed with respect to the user interface may include insurancepolicy details, valuation details, and/or other information associatedwith the trade secret, as described more fully elsewhere herein.

Additionally, or alternatively, the process 1700 may include storingfirst access-control data indicating a first identifier of a firstperson permitted to access the first record. The process 1700 may alsoinclude storing second access-control data indicating a secondidentifier of a second person permitted to access the second record. Inthese examples, the second access-control data may indicate that accessto the first record is unpermitted by the second person. The process1700 may also include receiving second input data requesting access tothe second record, where the second input data indicates that the secondperson is requesting access to the second record. The process 1700 mayalso include causing display, based at least in part on the second inputdata, of the second record including the selectable link. The process1700 may also include receiving third input data corresponding toselection of the selectable link and refraining from causing display ofthe first record based at least in part on the second access-controldata indicating that access to the first record is unpermitted.

Additionally, or alternatively, the process 1700 may includeassociating, using a smart contract associated with the blockchain, thetrade secret with an insurance policy, where the smart contractindicates a condition for validating the insurance policy. The process1700 may also include receiving, from the electronic device, validationdata indicating that the condition has been met and sending thevalidation data to the remote system associated with the insurer, wherethe validation data causes the smart contract to validate the insurancepolicy. The process 1700 may also include receiving, from the remotesystem, confirmation data indicating that the insurance policy has beenvalidated utilizing the smart contract.

Additionally, or alternatively, the process 1700 may include receiving,from the electronic device, valuation data indicated to be relevant to avalue of the trade secret. The process 1700 may also include receiving,from the electronic device, a third document obfuscation valuecorresponding to the valuation data and receiving, from at least one ofthe electronic device or the remote system, a second cryptographicdocument obfuscation value generated based at least in part on the thirddocument obfuscation value. In these examples, the second cryptographicdocument obfuscation value may represent a second block in theblockchain. Additionally, the first record may include the thirddocument obfuscation value and the second cryptographic documentobfuscation value.

Additionally, or alternatively, the process 1700 may include associatinga first feature vector with the first document based at least in part onfirst text data associated with the first document. The process 1700 mayalso include associating a second feature vector with the seconddocument based at least in part on second text data associated with thesecond document. The process 1700 may also include determining that adistance between the first feature vector and the second feature vectoris less than a threshold distance. In these examples, determining thatthe second document corresponds to the second version of the firstdocument may be based at least in part on the distance being less thanthe threshold distance. In other examples, the process 1700 may includedetermining a number of other feature vectors within a thresholddistance from the first feature vector and determining a popularityscore to associate with the first document based at least in part on thenumber of the other feature vectors.

Additionally, or alternatively, the process 1700 may include receivingan indication of a trade-secret type associated with the trade secretand identifying a frequency at which versions of trade secretsassociated with the trade-secret type are registered with the tradesecret registry. The process 1700 may also include generating aversion-registration alert based at least in part on the frequency andsending, to the electronic device, alert data representing theversion-registration alert.

Additionally, or alternatively, the process 1700 may include determininga frequency at which versions of trade secrets are registered with thetrade secret registry utilizing at least one of the electronic device oran entity identifier corresponding to an entity associated with theelectronic device. The process 1700 may also include generating aversion-registration alert based at least in part on the frequency andsending, to the electronic device, alert data representing theversion-registration alert.

FIG. 18 illustrates a flow diagram of an example process for digitalproperty management including trade secret valuation. The order in whichthe operations or steps are described is not intended to be construed asa limitation, and any number of the described operations may be combinedin any order and/or in parallel to implement process 1800.

At block 1802, the process 1800 may include storing, in association witha trade secret registry, a record indicating: a first documentobfuscation value corresponding to a document representing a tradesecret; and a first cryptographic document obfuscation value generatedbased at least in part on the first document obfuscation value, thefirst cryptographic document obfuscation value representing a firstblock in a blockchain of a remote system. For example, a systemassociated with the trade secret registry may store recordscorresponding to trade secrets registered with the trade secretregistry. Those records may include information such as documentobfuscation values generated based at least in part on documentsrepresenting the trade secrets. The document obfuscation values may begenerated by an electronic device of a user and/or by the systemassociated with the trade secret registry. Additionally, the electronicdevice and/or the system may request that the trade secret and/or thedocument obfuscation value be registered in association with ablockchain of a remote system. The remote system may register such tradesecrets and may generate cryptographic document obfuscation valuesrepresenting blocks of the blockchain.

At block 1804, the process 1800 may include receiving, from anelectronic device, valuation data indicated to be relevant to a value ofthe trade secret. For example, a user interface of the electronic devicemay include a selectable portion indicating an option to determine avalue for the trade secret. Based at least in part on selection of theselectable portion, the user interface may display a sequence of dialogboxes and/or input fields requesting information associated withdetermining a value of the trade secret. For example, a valuationcomponent may be configured to identify and/or determine a value toassociate with a given trade secret. The information requested by theinput fields may include, for example, the type of trade secret, animportance of the trade secret to the entity, entity revenue, entityvalue, date of trade secret creation, etc.

Additionally, in examples, the input fields may include a request forsupporting documents that include information that may be relevant tovaluation of the trade secret. In these examples, the user may identifythe supporting documents. A document obfuscation value may be generatedfor a given supporting document and/or the supporting document and/orthe document obfuscation value may be registered in association with theblockchain. The record for the trade secret may include informationassociated with the supporting document, such as the correspondingdocument obfuscation value and/or the cryptographic document obfuscationvalue corresponding to the block in the blockchain where the supportingdocument is registered.

In other examples, tag data generated as described herein may beutilized to determine some or all of the data described herein as beingutilized to determine a value of a trade secret. For example, the tagdata may be utilized to determine a trade-secret type. Trade secretshaving the same or a similar type may be analyzed to determine a valuefor a trade secret in question.

At block 1806, the process 1800 may include receiving, from theelectronic device, a second document obfuscation value corresponding tothe valuation data. The document obfuscation value may be generatedbased at least in part on the valuation data and may be generatedutilizing a obfuscation component as described elsewhere herein.

At block 1808, the process 1800 may include receiving, from at least oneof the electronic device or the remote system, a second cryptographicdocument obfuscation value generated based at least in part on thesecond document obfuscation value, the second cryptographic documentobfuscation value representing a second block in the blockchain. Inthese examples, the record may include the second document obfuscationvalue and the second cryptographic document obfuscation value. By sodoing, the valuation data may be registered with the blockchain, whichmay lend support to the determination of the valuation at a given time.

Additionally, or alternatively, the process 1800 may include receivingan indication that the first document represents a first version of thefirst document and receiving, from the electronic device, input datarequesting to register a second document in association with the tradesecret registry. The process 1800 may also include receiving, from theelectronic device, a third document obfuscation value corresponding tothe second document and determining, based at least in part on acomparison of the first document obfuscation value with the thirddocument obfuscation value, that the second document corresponds to asecond version of the first document. The process 1800 may also includegenerating a second record indicating that an identifier of the seconddocument has been registered in association with the trade secretregistry and indicating that the second document corresponds to thesecond version of the first document.

Additionally, or alternatively, the process 1800 may include storingfirst access-control data indicating a first identifier of a firstperson permitted to access a first portion of the record. The process1800 may also include storing second access-control data indicating asecond identifier of a second person permitted to access a secondportion of the record. In these examples, the second access-control datamay indicate that access to the first portion is unpermitted by thesecond person. The process 1800 may also include receiving second inputdata requesting access to the second portion, where the second inputdata indicates that the second person is requesting access to the secondrecord. The process 1800 may also include causing display, based atleast in part on the second input data, of the second portion. Theprocess 1800 may also include receiving third input data requestingaccess to the first portion of the record by the second person andrefraining from causing display of the first portion based at least inpart on the second access-control data indicating that access to thefirst portion is unpermitted.

Additionally, or alternatively, the process 1800 may includeassociating, using a smart contract associated with the blockchain, thetrade secret with an insurance policy, where the smart contractindicates a condition for validating the insurance policy. The process1800 may also include receiving, from the electronic device, validationdata indicating that the condition has been met and sending thevalidation data to the remote system associated with the insurer, wherethe validation data causes the smart contract to validate the insurancepolicy. The process 1800 may also include receiving, from the remotesystem, confirmation data indicating that the insurance policy has beenvalidated utilizing the smart contract.

FIG. 19 illustrates a flow diagram of an example process for digitalproperty management including access controls. The order in which theoperations or steps are described is not intended to be construed as alimitation, and any number of the described operations may be combinedin any order and/or in parallel to implement process 1900.

At block 1902, the process 1900 may include storing first access-controldata indicating: a first identifier of a first person permitted toaccess a record associated with a trade secret registry, the recordindicating a trade secret registered in association with the tradesecret registry; and a functionality of the trade secret registryauthorized for use by the first person. For example, the firstaccess-control data may be stored in association with the remote system.The access-control data may indicate who is authorized to view a givenrecord and/or given information associated with a record. In theseexamples, a user, to access a record, may be required to authenticatethe user's identity, such as by inputting a username and/or password,for example. The functionalities may include, for example, the abilityto view information, to manipulate information, to change accesscontrols, etc.

At block 1904, the process 1900 may include storing secondaccess-control data indicating: a second identifier of a second personpermitted to access the record; and that the second person isunauthorized to use the functionality. The second access-control datamay be stored in the same or a similar manner as the firstaccess-control data.

At block 1906, the process 1900 may include receiving first input datarequesting access to the record, the first input data indicating thatthe second person is requesting access to the record. The first inputdata may be received from an electronic device displaying a userinterface that allows a user to enter authentication information to gainaccess to information associated with the trade secret registry.

At block 1908, the process 1900 may include causing display, based atleast in part on the first input data, of the record. For example, giventhat the second access-control data indicates that the second person isauthorized to view the record, display of the record may be permitted.

At block 1910, the process 1900 may include receiving second input datarequesting use of the functionality. For example, the second person mayprovide input to the user interface of the electronic device tomanipulate information associated with the record, such as one or moretags associated with the record.

At block 1912, the process 1900 may include refraining from causing thefunctionality to be performed based at least in part on the secondaccess-control data indicating the second person is unauthorized to usethe functionality. For example, given that the second access-controldata indicates that the second person is unauthorized to utilize thefunctionalities, upon receiving input data requesting use of thefunctionality, the system may determine that such a request cannot beperformed based at least in part on the second access-control data.

Additionally, or alternatively, the process 1900 may include receivingan indication that the first trade secret represents a first version ofthe first trade secret and receiving, from the electronic device, inputdata requesting to register a second trade secret in association withthe trade secret registry. The process 1900 may also include receiving,from the electronic device, a document obfuscation value correspondingto the second trade secret and determining, based at least in part on acomparison of the document obfuscation values, that the second tradesecret corresponds to a second version of the first trade secret. Theprocess 1900 may also include generating a second record indicating thatan identifier of the second trade secret has been registered inassociation with the trade secret registry and indicating that thesecond trade secret corresponds to the second version of the first tradesecret.

Additionally, or alternatively, the process 1900 may include receiving,from the electronic device, valuation data indicated to be relevant to avalue of the trade secret. The process 1900 may also include receiving,from the electronic device, a document obfuscation value correspondingto the valuation data and receiving, from at least one of the electronicdevice or the remote system, a cryptographic document obfuscation valuegenerated based at least in part on the document obfuscation value. Inthese examples, the cryptographic document obfuscation value mayrepresent a block in the blockchain. Additionally, the record mayinclude the document obfuscation value and the cryptographic documentobfuscation value.

Additionally, or alternatively, the process 1900 may includeassociating, using a smart contract associated with the blockchain, thetrade secret with an insurance policy, where the smart contractindicates a condition for validating the insurance policy. The process1900 may also include receiving, from the electronic device, validationdata indicating that the condition has been met and sending thevalidation data to the remote system. The validation data may cause thesmart contract to validate the insurance policy. The process 1900 mayalso include receiving, from the remote system, confirmation dataindicating that the insurance policy has been validated utilizing thesmart contract.

Additionally, or alternatively, the process 1900 may include generatinga log of access to the record by one or more electronic devices. The logmay indicate an identifier of individual ones of persons that accessedrecord and/or a time value at which the individual ones of the personsaccessed the record. The process 1900 may also include receiving anindication that the first access-control data associated with the firstperson has been removed and generating alert data. The alert data mayindicate that the first person had access to the record and one or moretime values at which the first person accessed the record. The alertdata may further request confirmation that the first person hasundergone an exit interview associated with the trade secret.

Additionally, or alternatively, the process 1900 may include generatinga log of access to the record by one or more electronic devices. The logmay indicate an identifier of individual ones of persons that accessedrecord and/or a time value at which the individual ones of the personsaccessed the record. The process 1900 may also include generating, basedat least in part on the log, a compliance schedule associated with aninsurance policy relating to the trade secret. The compliance schedulemay indicate a time period during which compliance with a condition ofthe insurance policy may be performed by the first person. The process1900 may also include determining that the condition is unsatisfiedprior to the time period expiring and adjusting a payout valueassociated with the insurance policy based at least in part ondetermining that the condition is unsatisfied.

Additionally, or alternatively, the process 1900 may include generatingan interface to the trade secret registry that is configured to allowaccess to at least a portion of the trade secret registry via a remotedocketing system associated with intellectual property assets. Theprocess 1900 may also include sending access information for theinterface to the remote docketing system and receiving, from the remotedocketing system, a request to perform a search of the trade secretregistry. The request may include text data to be utilized to search thetrade secret registry. The process 1900 may also include identifyingresults of the search and sending results data representing the resultsto the remote docketing system.

Additionally, or alternatively, the process 1900 may include generatinga log of access to the record by one or more electronic devices anddetermining, based at least in part on the log, that the record has beenaccessed more than a threshold number of times during a time period. Theprocess 1900 may also include generating, based at least in part ondetermining that the record has been accessed more than the thresholdnumber of times during the time period, an alert indicating unusualactivity with respect to the record. The process 1900 may also includesending alert data representing the alert to an electronic deviceassociated with the record.

FIG. 20 illustrates a flow diagram of an example process for valuingproperty in accordance with a digital property authentication andmanagement system. The order in which the operations or steps aredescribed is not intended to be construed as a limitation, and anynumber of the described operations may be combined in any order and/orin parallel to implement process 2000.

At block 2002, the process 2000 may include storing, in association witha trade secret registry, a record indicating: a document obfuscationvalue corresponding to a document representing a trade secret; and acryptographic document obfuscation value generated based at least inpart on the document obfuscation value, the cryptographic documentobfuscation value representing a block in a blockchain of a remotesystem. For example, a system associated with the trade secret registrymay store records corresponding to trade secrets registered with thetrade secret registry. Those records may include information such asdocument obfuscation values generated based at least in part ondocuments representing the trade secrets. The document obfuscationvalues may be generated by an electronic device of a user and/or by thesystem associated with the trade secret registry. Additionally, theelectronic device and/or the system may request that the trade secretand/or the document obfuscation value be registered in association witha blockchain of a remote system. The remote system may register suchtrade secrets and may generate cryptographic document obfuscation valuesrepresenting blocks of the blockchain.

At block 2004, the process 2000 may include identifying tag dataindicating a characteristic associated with the document. For example, atag-data generator may be configured to generate tag data associatedwith the document. For example, one or more input fields may be causedto be displayed via user interface. The input fields may include arequest to “tag” or otherwise provide keywords for the document. Forexample, a document that corresponds to source code to operate a sewingmachine may be associated with keywords such as “source code,” “sewing,”“sewing machine,” “version 1.1.20,” etc. A user of the electronic devicemay input text corresponding to these tags and the tag-data generatormay utilize such input to generate the tag data. Additionally, oralternatively, the tag-data generator may automatically generate tagdata. For example, the tag-data generator may analyze the document to beregistered in association with the trade secret registry to identifykeywords associated with the document. For example, the tag-datagenerator may identify one or more fields of the document and/or valuesassociated with those fields. By way of illustration, the tag-datagenerator may identify a title field, a document-type field, one or moresections of the document, etc. The values, such as the text data,associated with these fields may be utilized to generate tags.Additionally, or alternatively, text data of the document may beanalyzed to determine which words are commonly used in the document.These words may be identified as keywords and may be utilized togenerate the tag data.

At block 2006, the process 2000 may include receiving, from anelectronic device, valuation data indicated to be relevant to a value ofthe trade secret. For example, a user interface of the electronic devicemay include a selectable portion indicating an option to determine avalue for the trade secret. Based at least in part on selection of theselectable portion, the user interface may display a sequence of dialogboxes and/or input fields requesting information associated withdetermining a value of the trade secret. For example, a valuationcomponent may be configured to identify and/or determine a value toassociate with a given trade secret. The information requested by theinput fields may include, for example, the type of trade secret, animportance of the trade secret to the entity, entity revenue, entityvalue, date of trade secret creation, etc.

Additionally, in examples, the input fields may include a request forsupporting documents that include information that may be relevant tovaluation of the trade secret. In these examples, the user may identifythe supporting documents. A document obfuscation value may be generatedfor a given supporting document and/or the supporting document and/orthe document obfuscation value may be registered in association with theblockchain. The record for the trade secret may include informationassociated with the supporting document, such as the correspondingdocument obfuscation value and/or the cryptographic document obfuscationvalue corresponding to the block in the blockchain where the supportingdocument is registered.

In other examples, tag data generated as described herein may beutilized to determine some or all of the data described herein as beingutilized to determine a value of a trade secret. For example, the tagdata may be utilized to determine a trade-secret type. Trade secretshaving the same or a similar type may be analyzed to determine a valuefor a trade secret in question.

At block 2008, the process 2000 may include determining the value of thetrade secret based at least in part on the tag data and the valuationdata. For example, a valuation component may utilize some or all of theinformation described with respect to block 2006 to determine a value ofthe trade secret.

At block 2010, the process 2000 may include causing an indication of thevalue to be displayed via a user interface accessible by the electronicdevice. For example, valuation details may be generated and stored inassociation with the record corresponding to the trade secret. Thevaluation details may include the determined value, the trade-secrettype, a creation date, an entity value, and/or a revenue value.Additionally, if supporting documents were provided to assist in thevaluation determination, a selectable link to those documents may alsobe displayed in connection with the record.

Additionally, or alternatively, the process 2000 may include receiving,from at least one of the electronic device or another device,entity-value data indicating at least one of an entity value for anentity associated with the document or an earnings and/or revenue valuefor the entity. In these examples, determining the value of the tradesecret may be based at least in part on the entity-value data.

Additionally, or alternatively, the process 2000 may include utilizing atime value associated with registration of the block in the blockchainwhen determining the value of the trade secret. In these examples, thevalue may increase as a period of time between the time value and acurrent time increases (either continuously, periodically, on ascheduled basis, or randomly).

Additionally, or alternatively, the process 2000 may include receiving,from the remote system, a second cryptographic document obfuscationvalue generated based at least in part on a second document obfuscationvalue corresponding to financial data associated with the trade secret.The second cryptographic document obfuscation value may represent asecond block in the blockchain of the remote system. In these examples,determining the value of the trade secret may be based at least in parton receiving the second cryptographic document obfuscation value.

FIG. 21 illustrates a flow diagram of an example process for provisionof insurance policies in accordance with a digital propertyauthentication and management system. The order in which the operationsor steps are described is not intended to be construed as a limitation,and any number of the described operations may be combined in any orderand/or in parallel to implement process 2100.

At block 2102, the process 2100 may include storing, in association witha trade secret registry, a record indicating: a document obfuscationvalue corresponding to a document representing a trade secret; and acryptographic document obfuscation value generated based at least inpart on the document obfuscation value, the cryptographic documentobfuscation value representing a block in a blockchain of a registrysystem. Those records may include information such as documentobfuscation values generated based at least in part on documentsrepresenting the trade secrets. The document obfuscation values may begenerated by an electronic device of a user and/or by the systemassociated with the trade secret registry. Additionally, the electronicdevice and/or the system may request that the trade secret and/or thedocument obfuscation value be registered in association with ablockchain of a remote system. The remote system may register such tradesecrets and may generate cryptographic document obfuscation valuesrepresenting blocks of the blockchain.

At block 2104, the process 2100 may include identifying tag dataindicating a characteristic associated with the document. For example, atag-data generator may be configured to generate tag data associatedwith the document. For example, one or more input fields may be causedto be displayed via user interface. The input fields may include arequest to “tag” or otherwise provide keywords for the document. Forexample, a document that corresponds to source code to operate a sewingmachine may be associated with keywords such as “source code,” “sewing,”“sewing machine,” “version 1.1.20,” etc. A user of the electronic devicemay input text corresponding to these tags and the tag-data generatormay utilize such input to generate the tag data. Additionally, oralternatively, the tag-data generator may automatically generate tagdata. For example, the tag-data generator may analyze the document to beregistered in association with the trade secret registry to identifykeywords associated with the document. For example, the tag-datagenerator may identify one or more fields of the document and/or valuesassociated with those fields. By way of illustration, the tag-datagenerator may identify a title field, a document-type field, one or moresections of the document, etc. The values, such as the text data,associated with these fields may be utilized to generate tags.Additionally, or alternatively, text data of the document may beanalyzed to determine which words are commonly used in the document.These words may be identified as keywords and may be utilized togenerate the tag data.

At block 2106, the process 2100 may include receiving, from anelectronic device, input data requesting issuance of an insurance policyassociated with the trade secret. For example, an electronic device maydisplay a user interface that may include a selectable portionindicating an option to apply for or otherwise acquire an insurancepolicy. Upon selection of the selectable portion, the input data may begenerated indicating that the user has selected the option to apply forthe insurance policy.

At block 2108, the process 2100 may include generating aninsurance-policy request indicating: that the trade secret has beenregistered with the trade secret registry; the cryptographic documentobfuscation value; and at least a portion of the tag data. For example,a policy component may be configured to assist in the provision of oneor more insurance policies for a given trade secret. The user interfacemay display one or more dialog boxes and/or input fields configured toreceive user input regarding provision of an insurance policy. Thisinformation may include, for example, a trade-secret type or category, avalue of the trade secret (either determined from above or identified bythe user), a policy period, an entity value, a date of creation of thetrade secret, and/or a portion enabling uploading of supporting and/orrequested documentation. In examples where supporting documentation isprovided, the supporting documentation may be registered with theblockchain in the same or a similar manner as described above withrespect to the supporting document for trade secret valuation.

At block 2110, the process 2100 may include sending the insurance-policyrequest to a distributed-ledger system associated with an insurer. Forexample, the policy component, and/or a communications component, may beconfigured to receive input data corresponding to the user input and maysend the input data to the distributed-ledger system, which isassociated with an insurer. The distributed-ledger system may processthe input data and, in examples, issue a policy insuring the tradesecret from, for example, misappropriation.

At block 2112, the process 2100 may include receiving, from thedistributed-ledger system, an indication that the insurance policy hasbeen issued. In these examples, confirmation data indicating that thepolicy has been issued and information associated with the policy may bereceived from the distributed-ledger system. This information may beincorporated into the record associated with the trade secret and may bedisplayed via the user interface, in examples. Some nonlimiting examplesof information associated with the insurance policy may include a policytype, a limit of liability, a retention value, a policy premium, apolicy form, a policy number, a policy period, a sub-limit of liability,and/or a valuation of the trade secret. Additionally, or alternatively,the information may include a payout value associated with an amount ofmoney to be paid to the entity associated with the trade secret upon theoccurrence of an event. In these examples, the policy component mayreceive compliance data indicating that the entity has not complied witha condition of the insurance policy and may cause display of updatedinsurance-policy information including an updated payout value. In theseexamples, the updated payout value may be less than the original payoutvalue. As the condition is met, the payout value may be updated toreflect compliance with the condition of the insurance policy.

At block 2114, the process 2100 may include causing the indication thatthe insurance policy has been issued to be displayed via a userinterface accessible by the electronic device. For example, theinformation associated with the policy may be incorporated into therecord associated with the trade secret and may be displayed via theuser interface, in examples.

Additionally, or alternatively, the process 2100 may include generatinga log of access to the record by one or more electronic devices. The logmay indicate an identifier of individual ones of persons that accessedthe record and/or a time value at which the individual ones of thepersons accessed the record. The process 2100 may also includegenerating, based at least in part on the log, a compliance scheduleassociated with the insurance policy. The compliance schedule mayindicate a time period during which compliance with a condition of theinsurance policy may be performed by at least one of the persons. Theprocess 2100 may also include determining that the condition isunsatisfied prior to the time period expiring and adjusting a payoutvalue associated with the insurance policy based at least in part ondetermining that the condition is unsatisfied. The process 2100 may alsoinclude generating, based at least in part on determining that thecondition is unsatisfied, alert data indicating that the condition isunsatisfied and sending the alert data to the one or more electronicdevices. In these examples, the alert data may cause a processor of theone or more electronic devices to initiate an application and display analert corresponding to the alert data.

Additionally, or alternatively, the process 2100 may include receiving,from the remote system, a second cryptographic document obfuscationvalue generated based at least in part on a second document obfuscationvalue corresponding to financial data associated with the trade secret.The second cryptographic document obfuscation value may represent asecond block in the blockchain of the remote system. In these examples,the insurance-policy request may include the second cryptographicdocument obfuscation value and/or an indication thereof.

Additionally, or alternatively, the process 2100 may includedetermining, based at least in part on the record, a value of the tradesecret. In these examples, the insurance-policy request includes thevalue of the trade secret.

FIG. 22 illustrates a flow diagram of an example process for propertyverification in accordance with a digital property authentication andmanagement system. The order in which the operations or steps aredescribed is not intended to be construed as a limitation, and anynumber of the described operations may be combined in any order and/orin parallel to implement process 2200.

At block 2202, the process 2200 may include storing, in association witha trade secret registry, a record indicating: a first documentobfuscation value corresponding to a first document representing a tradesecret; and a cryptographic document obfuscation value generated basedat least in part on the first document obfuscation value, thecryptographic document obfuscation value representing a block in ablockchain of a remote system. Those records may include informationsuch as document obfuscation values generated based at least in part ondocuments representing the trade secrets. The document obfuscationvalues may be generated by an electronic device of a user and/or by thesystem associated with the trade secret registry. Additionally, theelectronic device and/or the system may request that the trade secretand/or the document obfuscation value be registered in association witha blockchain of a remote system. The remote system may register suchtrade secrets and may generate cryptographic document obfuscation valuesrepresenting blocks of the blockchain.

At block 2204, the process 2200 may include receiving, from anelectronic device, a second document indicated to have beenmisappropriated. For example, the accused document may be identified,such as via a user interface of the electronic device.

At block 2206, the process 2200 may include receiving, from theelectronic device, input data requesting verification that the seconddocument corresponds to a registered document registered with respect tothe trade secret registry. The input data may be received from theelectronic device displaying the user interface.

At block 2208, the process 2200 may include generating, based at leastin part on the second document, a second document obfuscation valuecorresponding to the second document. For example, a documentobfuscation value may be generated for the accused document in the sameor a similar manner as described above with respect to the obfuscationcomponent(s). The verification component may be utilized to analyze thedocument obfuscation value for the accused document with respect toother document obfuscation values of registered documents.

At block 2210, the process 2200 may include determining a degree ofsimilarity between the first document obfuscation value and the seconddocument obfuscation value. For example, a comparison component may beconfigured to analyze the document obfuscation values and determinedegrees of similarity and/or degrees or differences between the documentobfuscation values and/or the documents corresponding to the documentobfuscation values. In other examples, a feature vector may beassociated with some or all of the document obfuscation values. Thefeature vector may correspond to characteristics of the documentobfuscation value and/or the document. For example, the presence orabsence of text data and/or image data from the document may impact thefeature vector. In other examples, the text data and/or image dataitself may impact the feature vector. Other factors such as documentlength, the entity associated with the document, creation date,modification date, and/or other metadata may impact the feature vector.By way of example, a feature may be described as an individualmeasurable property or characteristic of a document. A given feature maybe numeric and/or may be considered a string and/or a graphic. A set ofsuch features may be described as a feature vector. As such, similarfeature vectors indicate similar characteristics and/or properties ofthe documents they represent.

In other examples, Levenshtein distances may be utilized to determine adegree of similarity between trade secrets. A Levenshtein distance maybe determined between two document obfuscation values and/or documents.A shorter Levenshtein distance may indicate more similarity than alonger Levenshtein distance. As used herein, a Levenshtein distance,also known as an edit distance, may be described as a string metric formeasuring the difference between two sequences. For example, theLevenshtein distance between two words may be considered the minimumnumber of single-character edits to change one word into the other. Assuch, the Levenshtein distance between two very similar words would beshorter than a Levenshtein distance between two very different words. Inthese examples, a Levenshtein distance may be determined between twodocuments and/or two document obfuscation values representing thosedocuments, with shorter Levenshtein distances indicating more similaritybetween documents.

At block 2212, the process 2200 may include determining that the degreeof similarity is greater than a threshold degree of similarity. Forexample, a threshold degree of similarity may be identified and/ordetermined and the degree of similarity between document obfuscationvalues may be compared to the threshold degree of similarity. Documentobfuscation values with a degree of similarity that meets or exceeds thethreshold degree of similarity may be determined to be similar, whilehash-value pairs that fall below the threshold degree of similarity maybe determined to be dissimilar. Additionally, document obfuscationvalues may be segmented and the segments may be compared to determineportions of the document obfuscation values that are similar andportions that are not. The number of similar versus dissimilar documentobfuscation values may be utilized to determine an overall degree ofsimilarity between document obfuscation values. By way of additionalexample, the process 2200 may include determining that a Levenshteindistance between first characteristics of the first document and secondcharacteristics of the second document is less than a thresholdLevenshtein distance.

At block 2214, the process 2200 may include determining that the seconddocument corresponds to the first document based at least in part on thedegree of similarity being greater than the threshold degree ofsimilarity. If the verification component determines that at least oneof the registered document obfuscation values matches the documentobfuscation value for the accused document, the verification componentmay determine that the accused document is the same or similar to theregistered document. In other examples, the verification component maydetermine a degree of similarity between the accused document and one ormore registered documents. In these examples, the accused document maybe determined to be similar to a registered document when the degree ofsimilarity meets or exceeds a threshold degree of similarity. In stillother examples, the verification component may be configured todetermine which portions of an accused document match or are similar toat least one registered document. An indication of the matching orsimilar portions may be displayed, such as via the user interface.Additionally, in instances where multiple versions of a document havebeen registered, the verification component may be configured todetermine which of the multiple versions is most similar to the accuseddocument, and may provide an indication of the version that is mostsimilar.

Additionally, or alternatively, the process 2200 may include sending, toa remote system associated with the blockchain, a request to identify asecond cryptographic document obfuscation value corresponding to thesecond document and/or a second hash corresponding to the seconddocument. The process 2200 may also include receiving the secondcryptographic document obfuscation value and determining that the firstcryptographic document obfuscation value corresponds to the secondcryptographic document obfuscation value. In these examples, determiningthat the second document corresponds to the first document may be basedat least in part on the first cryptographic document obfuscation valuecorresponding to the second cryptographic document obfuscation value.

FIG. 23 illustrates a flow diagram of another example process forproperty verification in accordance with a digital propertyauthentication and management system. The order in which the operationsor steps are described is not intended to be construed as a limitation,and any number of the described operations may be combined in any orderand/or in parallel to implement process 2300.

At block 2302, the process 2300 may include storing a record indicating:a first document obfuscation value corresponding to a first documentrepresenting a trade secret; and a cryptographic document obfuscationvalue generated based at least in part on the first document obfuscationvalue, the cryptographic document obfuscation value representing a blockin a blockchain of a remote system. Those records may includeinformation such as document obfuscation values generated based at leastin part on documents representing the trade secrets. The documentobfuscation values may be generated by an electronic device of a userand/or by the system associated with the trade secret registry.Additionally, the electronic device and/or the system may request thatthe trade secret and/or the document obfuscation value be registered inassociation with a blockchain of a remote system. The remote system mayregister such trade secrets and may generate cryptographic documentobfuscation values representing blocks of the blockchain.

At block 2304, the process 2300 may include receiving, from anelectronic device, a second document indicated to have beenmisappropriated. For example, the accused document may be identified,such as via a user interface of the electronic device.

At block 2306, the process 2300 may include generating, based at leastin part on the second document, a second document obfuscation valuecorresponding to the second document. For example, a documentobfuscation value may be generated for the accused document in the sameor a similar manner as described above with respect to the obfuscationcomponent(s). The verification component may be utilized to analyze thedocument obfuscation value for the accused document with respect toother document obfuscation values of registered documents.

At block 2308, the process 2300 may include determining a degree ofsimilarity between the first document obfuscation value and the seconddocument obfuscation value. For example, a comparison component may beconfigured to analyze the document obfuscation values and determinedegrees of similarity and/or degrees or differences between the documentobfuscation values and/or the documents corresponding to the documentobfuscation values. In other examples, a feature vector may beassociated with some or all of the document obfuscation values. Thefeature vector may correspond to characteristics of the documentobfuscation value and/or the document. For example, the presence orabsence of text data and/or image data from the document may impact thefeature vector. In other examples, the text data and/or image dataitself may impact the feature vector. Other factors such as documentlength, the entity associated with the document, creation date,modification date, and/or other metadata may impact the feature vector.By way of example, a feature may be described as an individualmeasurable property or characteristic of a document. A given feature maybe numeric and/or may be considered a string and/or a graphic. A set ofsuch features may be described as a feature vector. As such, similarfeature vectors indicate similar characteristics and/or properties ofthe documents they represent.

In other examples, Levenshtein distances may be utilized to determine adegree of similarity between trade secrets. A Levenshtein distance maybe determined between two document obfuscation values and/or documents.A shorter Levenshtein distance may indicate more similarity than alonger Levenshtein distance. As used herein, a Levenshtein distance,also known as an edit distance, may be described as a string metric formeasuring the difference between two sequences. For example, theLevenshtein distance between two words may be considered the minimumnumber of single-character edits to change one word into the other. Assuch, the Levenshtein distance between two very similar words would beshorter than a Levenshtein distance between two very different words. Inthese examples, a Levenshtein distance may be determined between twodocuments and/or two document obfuscation values representing thosedocuments, with shorter Levenshtein distances indicating more similaritybetween documents.

At block 2310, the process 2300 may include determining that the seconddocument corresponds to the first document based at least in part on thedegree of similarity. If the verification component determines that atleast one of the registered document obfuscation values matches thedocument obfuscation value for the accused document, the verificationcomponent may determine that the accused document is the same or similarto the registered document. In other examples, the verificationcomponent may determine a degree of similarity between the accuseddocument and one or more registered documents. In these examples, theaccused document may be determined to be similar to a registereddocument when the degree of similarity meets or exceeds a thresholddegree of similarity. In still other examples, the verificationcomponent may be configured to determine which portions of an accuseddocument match or are similar to at least one registered document. Anindication of the matching or similar portions may be displayed, such asvia the user interface. Additionally, in instances where multipleversions of a document have been registered, the verification componentmay be configured to determine which of the multiple versions is mostsimilar to the accused document, and may provide an indication of theversion that is most similar.

Additionally, or alternatively, the process 2300 may include sending, toa remote system associated with the blockchain, a request to identify asecond cryptographic document obfuscation value corresponding to thesecond document and/or a second hash corresponding to the seconddocument. The process 2300 may also include receiving the secondcryptographic document obfuscation value and determining that the firstcryptographic document obfuscation value corresponds to the secondcryptographic document obfuscation value. In these examples, determiningthat the second document corresponds to the first document may be basedat least in part on the first cryptographic document obfuscation valuecorresponding to the second cryptographic document obfuscation value.

Additionally, or alternatively, the process 2300 may include storing asecond record associated with a second version of the first document,where the second record may be associated with the first record based atleast in part on the second record being associated with the secondversion of the first document. The process 2300 may also includedetermining a second degree of similarity between a third documentobfuscation value corresponding to the second version of the firstdocument and the second document obfuscation value. In these examples,determining that the second document corresponds to the first documentmay include determining that the second document corresponds to thesecond version of the first document based at least in part on thesecond degree of similarity.

Additionally, or alternatively, the process 2300 may include causing asequence of dialog boxes to be displayed via a user interface of theelectronic device. Causing the sequence of dialog boxes to be displayedmay be based at least in part on determining that the second documentcorresponds to the first document. In these examples, the sequence ofdialog boxes may include text associated with submitting a claim forinsurance coverage in association with an insurance policy for the tradesecret. The process 2300 may also include receiving input data includinga response to the text and sending, to a distributed-ledger systemassociated with an insurer, at least one of the input data and/or anotification of the claims. The process 2300 may also include receiving,from the distributed-ledger system, status data indicating thatinformation is requested to process the claim. The process 2300 may alsoinclude sending, to the electronic device, an alert indicating that theinformation is requested, where the alert includes a selectable portion.The process 2300 may also include causing display, via a user interfaceand based at least in part on receiving an indication that theselectable portion has been selected, of a request for the information.

Additionally, or alternatively, the process 2300 may include determininga first portion of the first document obfuscation value that correspondsto a second portion of the second document obfuscation value andidentifying a third portion of the first document that corresponds tothe first portion of the first document obfuscation value. The process2300 may also include causing display, via the user interface and basedat least in part on identifying the third portion, of an indication thatthe third portion of the first document is similar to at least a portionof the second document.

While the foregoing invention is described with respect to the specificexamples, it is to be understood that the scope of the invention is notlimited to these specific examples. Since other modifications andchanges varied to fit particular operating requirements and environmentswill be apparent to those skilled in the art, the invention is notconsidered limited to the example chosen for purposes of disclosure, andcovers all changes and modifications which do not constitute departuresfrom the true spirit and scope of this invention.

Although the application describes embodiments having specificstructural features and/or methodological acts, it is to be understoodthat the claims are not necessarily limited to the specific features oracts described. Rather, the specific features and acts are merelyillustrative some embodiments that fall within the scope of the claims.

1. (canceled)
 2. A system comprising: one or more processors; andnon-transitory computer-readable media storing computer-executableinstructions that, when executed by the one or more processors, causethe one or more processors to perform operations comprising: receiving adocument representing a digital property; receiving first inputindicating that the document is to be registered in a digital propertyregistry associated with a remote registry system; generating, based atleast in part on receiving the input, a document obfuscation valuerepresenting the document; sending, to the remote registry system: thedocument obfuscation value; and a first request to register the digitalproperty in association with the digital property registry; andreceiving, from the remote registry system, first data indicating thatthe remote registry system has generated a record in the digitalproperty registry in response to the first request, the recordindicating the digital property has been registered in association withthe digital property registry and the digital property has beenassociated with a block value representing a block in a blockchainassociated with a distributed-ledger system; receiving user inputrequesting that the record for the digital property be associated withan insurance policy; and sending, to an insurer system associated withan insurer, at least the user input.
 3. The system of claim 2, whereinthe document obfuscation value comprises a first document obfuscationvalue, and the operations further comprise: identifying a first portionof the document and a second portion of the document; generating asecond document obfuscation value representing the first portion of thedocument; generating a third document obfuscation value representing thesecond portion of the document; and wherein generating the firstdocument obfuscation value comprises generating the first documentobfuscation value based at least in part on the second documentobfuscation value and the third document obfuscation value.
 4. Thesystem of claim 2, wherein the block comprises a first block, theblockchain comprises a first blockchain, the block value comprises afirst block value, and the operations further comprise: sending, to theinsurer system, the document obfuscation value and a second request togenerate a second block in a second blockchain associated with theinsurer system; receiving, from the insurer system, a second block valuerepresenting the second block in the second blockchain; sending, thesecond block value to the remote registry system; and wherein the recordassociates the second block value with the digital property.
 5. Thesystem of claim 2, wherein the document obfuscation value comprises afirst document obfuscation value, the block comprises a first block, theblockchain comprises a first blockchain, the block value comprises afirst block value, the distributed-ledger system comprises a firstdistributed-ledger system, generating the first document obfuscationvalue comprises generating the first document obfuscation valueutilizing a first hash-value generator, and the operations furthercomprise: generating a second document obfuscation value representingthe document, the second document obfuscation value generated utilizinga second hash-value generator that differs from the first hash-valuegenerator; sending the second document obfuscation value to the remoteregistry system; and wherein the record indicates that the digitalproperty has been associated with a second block value associated withthe second document obfuscation value, the second block valuerepresenting a second block in a second blockchain associated with asecond distributed-ledger system.
 6. The system of claim 2, theoperations further comprising: receiving second input indicating atleast one of a person or an entity associated with the document;generating tag data based at least in part on the second input;receiving third input requesting a search of the digital propertyregistry, the third input including a search term; causing the tag datato be searched based at least in part on the search term; and generatingresponse data indicating a result of the search of at least the tagdata.
 7. The system of claim 2, the operations further comprising:identifying fields of the document, individual ones of the fields beingassociated with a field type; identifying a field value associated withthe individual ones of the fields; and generating tag data associatedwith the document, the tag data generated based at least in part on thefield type and the field value for the individual ones of the fields. 8.The system of claim 2, wherein the document comprises a first document,the document obfuscation value comprises a first document obfuscationvalue, and the operations further comprise: receiving input datarequesting verification that a second document corresponds to the firstdocument; generating, based at least in part on the second document, asecond document obfuscation value corresponding to the second document;determining that the first document obfuscation value corresponds to thesecond document obfuscation value; and determining that the seconddocument corresponds to the first document based at least in part on thefirst document obfuscation value corresponding to the second documentobfuscation value.
 9. The system of claim 2, wherein the recordcomprises a first record, and the operations further comprise: sending,to the remote registry system, an identifier corresponding to at leastone of: an electronic device that maintains the document; or an entityassociated with the electronic device; and receiving, from the remoteregistry system, second data indicating: the identifier has beenassociated with the first record; a second record associated with thedigital property registry is associated with the identifier; and thefirst record has been associated with the second record based at leastin part on the first record and the second record being associated withthe identifier.
 10. The system of claim 2, the operations furthercomprising: analyzing the document obfuscation value in relation tostored document obfuscation values; determining, based at least in parton analyzing the document obfuscation value in relation to the storeddocument obfuscation values, that the document obfuscation value isdifferent from the stored document obfuscation values; and whereinsending the first request to the remote registry system comprisessending the first request to the remote registry system based at leastin part on the document obfuscation value being different from thestored document obfuscation values.
 11. The system of claim 10, whereindetermining that the document obfuscation value is different from thestored document obfuscation values comprises determining that thedocument obfuscation value is different from the stored documentobfuscation values based at least in part on: determining a degree ofdifference between the document obfuscation value and the storeddocument obfuscation values; and determining that the degree ofdifference is greater than a threshold degree of difference.
 12. Amethod comprising: receiving a document representing a digital property;receiving first input indicating that the document is to be registeredin a digital property registry associated with a remote registry system;generating, based at least in part on receiving the input, a documentobfuscation value representing the document; sending, to the remoteregistry system: the document obfuscation value; and a first request toregister the digital property in association with the digital propertyregistry; and receiving, from the remote registry system, first dataindicating that the remote registry system has generated a record in thedigital property registry in response to the first request, the recordindicating the digital property has been registered in association withthe digital property registry and the digital property has beenassociated with a block value representing a block in a blockchainassociated with a distributed-ledger system; receiving user inputrequesting that the record for the digital property be associated withan insurance policy; and sending, to an insurer system associated withan insurer, at least the user input.
 13. The method of claim 12, whereinthe document obfuscation value comprises a first document obfuscationvalue, and the method further comprises: identifying a first portion ofthe document and a second portion of the document; generating a seconddocument obfuscation value representing the first portion of thedocument; generating a third document obfuscation value representing thesecond portion of the document; and wherein generating the firstdocument obfuscation value comprises generating the first documentobfuscation value based at least in part on the second documentobfuscation value and the third document obfuscation value.
 14. Themethod of claim 12, wherein the block comprises a first block, theblockchain comprises a first blockchain, the block value comprises afirst block value, and the method further comprises: sending, to theinsurer system, the document obfuscation value and a second request togenerate a second block in a second blockchain associated with theinsurer system; receiving, from the insurer system, a second block valuerepresenting the second block in the second blockchain; sending, thesecond block value to the remote registry system; and wherein the recordassociates the second block value with the digital property.
 15. Themethod of claim 12, wherein the document obfuscation value comprises afirst document obfuscation value, the block comprises a first block, theblockchain comprises a first blockchain, the block value comprises afirst block value, the distributed-ledger system comprises a firstdistributed-ledger system, generating the first document obfuscationvalue comprises generating the first document obfuscation valueutilizing a first hash-value generator, and the method furthercomprises: generating a second document obfuscation value representingthe document, the second document obfuscation value generated utilizinga second hash-value generator that differs from the first hash-valuegenerator; sending the second document obfuscation value to the remoteregistry system; and wherein the record indicates that the digitalproperty has been associated with a second block value associated withthe second document obfuscation value, the second block valuerepresenting a second block in a second blockchain associated with asecond distributed-ledger system.
 16. The method of claim 12, furthercomprising: receiving second input indicating at least one of a personor an entity associated with the document; generating tag data based atleast in part on the second input; receiving third input requesting asearch of the digital property registry, the third input including asearch term; causing the tag data to be searched based at least in parton the search term; and generating response data indicating a result ofthe search of at least the tag data.
 17. The method of claim 12, furthercomprising: identifying fields of the document, individual ones of thefields being associated with a field type; identifying a field valueassociated with the individual ones of the fields; and generating tagdata associated with the document, the tag data generated based at leastin part on the field type and the field value for the individual ones ofthe fields.
 18. The method of claim 12, wherein the document comprises afirst document, the document obfuscation value comprises a firstdocument obfuscation value, and the method further comprises: receivinginput data requesting verification that a second document corresponds tothe first document; generating, based at least in part on the seconddocument, a second document obfuscation value corresponding to thesecond document; determining that the first document obfuscation valuecorresponds to the second document obfuscation value; and determiningthat the second document corresponds to the first document based atleast in part on the first document obfuscation value corresponding tothe second document obfuscation value.
 19. The method of claim 12,wherein the record comprises a first record, and the method furthercomprises: sending, to the remote registry system, an identifiercorresponding to at least one of: an electronic device that maintainsthe document; or an entity associated with the electronic device; andreceiving, from the remote registry system, second data indicating: theidentifier has been associated with the first record; a second recordassociated with the digital property registry is associated with theidentifier; and the first record has been associated with the secondrecord based at least in part on the first record and the second recordbeing associated with the identifier.
 20. The method of claim 12,further comprising: analyzing the document obfuscation value in relationto stored document obfuscation values; determining, based at least inpart on analyzing the document obfuscation value in relation to thestored document obfuscation values, that the document obfuscation valueis different from the stored document obfuscation values; and whereinsending the first request to the remote registry system comprisessending the first request to the remote registry system based at leastin part on the document obfuscation value being different from thestored document obfuscation values.
 21. The method of claim 20, whereindetermining that the document obfuscation value is different from thestored document obfuscation values comprises determining that thedocument obfuscation value is different from the stored documentobfuscation values based at least in part on: determining a degree ofdifference between the document obfuscation value and the storeddocument obfuscation values; and determining that the degree ofdifference is greater than a threshold degree of difference.